search for: stpierr

...better and in much more detail than I could, so I'll let him speak for me. Unfortunately, I don't have the same solution. nss_ldap is configured properly, and things like 'getent passwd' and 'id machine-acct$' show the machine accounts as expected: % getent passwd | grep stpierre stpierre:x:2273:4000:Christopher St Pierre:/home/faculty/stpierre:/bin/zsh stpierre-pc$:*:1944:1000:Computer:/dev/null:/bin/false % id stpierre-pc$ uid=1944(stpierre-pc$) gid=1000 groups=1000 Unfortunately, "fix nss_ldap" is about the only suggestion I could find on this problem on Goog...

...to an rid, prepend my system sid, and write it to the sambaSID attribute. Here's the log excerpt that lead me to believe that it's having problems with the SID: [...snip...] [2004/10/04 14:57:39, 10] passdb/pdb_get_set.c:pdb_set_nt_username(679) pdb_set_nt_username: setting nt username stpierre, was [2004/10/04 14:57:39, 10] passdb/pdb_get_set.c:pdb_set_init_flags(525) element 15 -> now SET [2004/10/04 14:57:39, 10] lib/smbldap.c:smbldap_get_single_attribute(309) smbldap_get_single_attribute: [sambaSID] = [<does not exist>] [2004/10/04 14:57:39, 10] lib/smbldap.c:smbldap_ge...

...not sure when the most recent one joined, though, but I'm reasonably sure nothing has changed since then. The Samba log gives the following when I try to the computer to the domain: [2006/02/28 15:33:02, 2] passdb/pdb_ldap.c:init_sam_from_ldap(499) init_sam_from_ldap: Entry found for user: stpierre [2006/02/28 15:33:02, 2] passdb/pdb_ldap.c:init_group_from_ldap(2001) init_group_from_ldap: Entry found for group: 1004 [2006/02/28 15:33:02, 2] auth/auth.c:check_ntlm_password(307) check_ntlm_password: authentication for user [stpierre] -> [stpierre] -> [stpierre] succeeded [2006/02/...

This is an immensely frustrating problem. I try to logon to my Samba 3.0.11 PDC running on SuSE, and the Samba logs report that it all went swimmingly: [2005/06/02 16:34:45, 2] auth/auth.c:check_ntlm_password(305) check_ntlm_password: authentication for user [stpierre] -> [stpierre] -> [stpierre] succeeded So w00t, right. But no! Windows rejects my login with a "bad password" error. The strange thing is that I can mount volumes from that server without a problem -- it's only domain logons that are broken. Googling didn't turn up m...

I have a small domain with a Samba PDB and two Windows clients. My goal is to have all accounts held centrally on the Linux box, but the administrator login doesn't work as an administrator. That is, I can login just fine as 'administrator' (or as any of the other accounts in the Samba password db), but I don't get administrative privileges in Windows. In smb.conf, I have:

I'm trying to troubleshoot a nasty problem with Samba 2.2.8a that I asked about here a while back, and I need someone with a working LDAP-Samba PDC -- preferably 2.2.8a, ideally running on Mac OS X, but I'll take what I can get -- to post the results of an ldapsearch for one of their machine trust accounts. All I'd need is the results of a command along these lines: ldapsearch -LLL

...centos /bin/cat /etc/centos-release CentOS Linux release 7.0.1406 (Core) To use the CentOS-6 image, you must specify the tag in the command: [jperrin at lappy ~]$ docker run -i -t centos:centos6 /bin/cat /etc/centos-release CentOS release 6.5 (Final) ===== Thanks We would like to thank Chris StPierre for his initial work with docker, and developing the kickstarts used for the build process. - -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJTvWLUAAoJEBbHyC76Ca...

...centos /bin/cat /etc/centos-release CentOS Linux release 7.0.1406 (Core) To use the CentOS-6 image, you must specify the tag in the command: [jperrin at lappy ~]$ docker run -i -t centos:centos6 /bin/cat /etc/centos-release CentOS release 6.5 (Final) ===== Thanks We would like to thank Chris StPierre for his initial work with docker, and developing the kickstarts used for the build process. - -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJTvWLUAAoJEBbHyC76Ca...

I'm trying to get an LDAP PDC running, and when I try to join a Windows computer to the domain, I get the following error: "The specified domain either does not exist or could not be contacted" That's from Win2K. WinXP gives more information: ------------------------------------------- The domain name NWU_FLUFFY might be a NetBIOS domain name. If this is the case, verify

I've got a file server running both Samba and Netatalk ([OT] which are two programs that dearly need to be rolled into one). I've *tried* to configure it to minimize problems between the two, but I've run into a problem where users can't delete folders that contain, e.g., .AppleDouble folders in them. When I try from smbclient, I get: NT_STATUS_DIRECTORY_NOT_EMPTY removing

When a user tries logging in and enters the wrong password a few times in a row, their account becomes disabled. Is there a way to prevent this behavior? I couldn't find anything in the smb.conf man page about it. Alternatively, could we use a preexec script to just re-enable all accounts when there's a logon attempt? Or does that script only get executed after a user is authenticated?

I am trying to set up Samba 2.2.9 on a SuSE 9.1 box as an LDAP PDC whose only job will be authentication. Our LDAP server is on a separate box. I can join the domain just fine, but when I try to login via Windows, I get the following error: "The system cannot log you on to this domain because the system's computer account in its primary domain is missing or the password on that account

Samba 3.0.21c, RHEL4. About a week ago, we restarted our Samba server because nmbd had run amok. Since that restart, our Apple clients have periodically disconnected -- by most reports, they disconnect every 15-45 minutes. It doesn't appear to be synchronized, i.e., every Mac on campus doesn't disconnect at once, but only occasionally. They get a message similar to: "A server you

A few computers -- two or three -- are very spotty about letting people log on. It seems -- and this could be off-base -- that they'll let anyone log on once, but will require a reboot before you can log on again. Sometimes, logging on works fine, though. There really appears to be little rhyme or reason to what happens. In the Samba logs, I'm getting: [2006/10/20 08:08:14, 0]

I'm trying to get Samba on a Mac OS X box running as a PDC with an LDAP backend. I've read through all of the major walkthroughs I can find, and we've actually already got it running very nicely as a file server; people are currently authenticating against a different PDC and then mapping drives from the Samba box in question. However, I'd like it to be the PDC eventually, but

I had a problem similar to my current one a week or so ago, and I was encouraged to upgrade from Samba 2.2.9 to 3.0.7, which I did. Now that I've completed that nightmare, the problem I initially set out to fix is still there, just different. Namely: I am trying to set up Samba 3.0.7 on a SuSE 9.1 box as an LDAP PDC whose only job will be authentication. Our LDAP server is on a separate