search for: skain

I have 3.0.2a (with about 75 machines/users) installed as a PDC for my Win2k users and found an oddity. (waiting for a bin version of 3.0.3 for RH8.0) All was fine before I left 2.2.8.... But now when users hit <CTL>-<ALT>-<DEL> and change the password, they get "domain not available". When they log in, they get the logon scripts to execute, and anything else I do to

After much searching, research, compiling, and some guess work, I found my problem was wrapped around one simple fact. I didn't have the samba.schema included. I now have some suggestions: 1. If you are going to force people to use something complex, DOCUMENT it. Assume there are people like me who have no understanding of ldap. Even some automatic script should be written for people who

Someone emailed me directly when I was asking about the 8.0 RPMs, and why I didn't just compile it. Due to the production nature of our servers which run practially 24/7, I can do an "rpm -Uhv samba.rpm" and then do an "smb restart" with very little impact. If I move to non-rpm versions, I am forced to compile first, remove the RPM, which is a longer downtime, then install

...attached to a Windows 2003 server. I am cheating, using RPC rather than ADS. So here is the issue. Generally everything works. I do a wbinfo -u and all comes back. I do a getent passwd and a good list comes back as well. The problem is sometimes with individual users, I do a "getent passwd jskains" and it will come back blank. But then I do it again and it comes back with a good entry. Why???????????? This is so fustrating because other services are effected by this. For example, If I change permissions on a file with "chown jskains file" sometimes it will say "invalid u...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After upgrading from 3.0.2 to 3.0.3 in a Windows 2000 Native Domain environment, 9x clients can't connect and wbinfo -t doesn't work: bash-2.05a# wbinfo -t checking the trust secret via RPC calls failed error code was NT_STATUS_PIPE_NOT_AVAILABLE (0xc00000ac) Could not check secret Downgrading to 3.0.2 fixes this. I can get log files, but

Just in case anyone cares, I still have to run a Redhat 8.0 server, so if someone could keep the 8.0 RPMs going, I'd greatly appreciate it. As it stands, the 8.0 on the samba.org website are pretty bare. JMS

On my Redhat 7.3 machine (soon to be upgraded) using printcap style printers, it has stopped sharing them when I went to 3.0.4.. It was on 3.0.2a... Thoughts? JMS

Ok.. I figured a lot of this out... But I am lost on how to keep the UID and GIDs identical. How do I make sure system A uses the same IDs that system B will use? JMS -----Original Message----- From: samba-bounces+jskains=deltad.com@lists.samba.org [mailto:samba-bounces+jskains=deltad.com@lists.samba.org]On Behalf Of Josh Skains Sent: Wednesday, June 09, 2004 4:45 PM To: samba@lists.samba.org Subject: [Samba] Winbind My first stab at winbind gets: [2004/06/09 09:19:17, 1] nsswitch/winbindd_user.c:winbindd_fill_p...

Well, I am a bit confused. I am DESPRATE to get winbind to use the same GID and UIDs on several machines... But I am having a headache doing it. I need to run an LDAP server, I guess, so I put one together with the most basic things. But I just simply can't get it to run. Is there any site or document I can read that will show a most basic LDAP setup that would run my idmaps? I just need LDAP

Sorry.. One more email.. I tried to create the IDMAP container on the LDAP with an example I found: dn: ou=Idmap,dc=softeng,dc=com objectClass: organizationalUnit ou: idmap structuralObjectClass: organizationalUnit and it gives: adding new entry "ou=Idmap,dc=softeng,dc=com" ldap_add: Constraint violation additional info: structuralObjectClass: no user modification allowed

...e windows DC, and that when that user tries to log into one of our Linux boxes, they would be able to use the same login and password. Finally, if I happen to have several Linux boxes, and I wanted to ensure identical UID/GIDs, that LDAP is the only answer to make that happen. In other words, if jskains is assigned 10000 as a UID on System A and if jskains logs into System B (another Linux box), LDAP would be used to ensure that jskains remains at UID 10000. In that case if System A and System B happen to share an NFS mount, file ownerships would remain intact. So I am basically trying to ensur...