Well that's because I started out using the following: passdb backend = tdbsam:/etc/samba/passdb.tdb unixsam
Through debugging and trial and error I ended up with the smb.conf I sent you. The only reason I'm using smbpasswd format now is because I can verify that all machine accounts are listed. But it really doesn't matter which backend I use, they both don't work smbpasswd or tdbsam. Plus theoretically they both should have the same information since smbpasswd was generated from an expert I performed on tdbsam using pdbedit -e. Really appreciate your assistance!! IRV -----Original Message----- From: Steve Langasek [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 03, 2002 5:36 PM To: Irving Carrion Cc: 'samba list' Subject: Re: Machine accounts are no longer recognized in SAMBA 3.0-20-4 Irving, On Tue, Dec 03, 2002 at 05:26:42PM -0500, Irving Carrion wrote: > After verifying my smb.conf file, the only thing that changed was this > "panic action" command was added. My smb.conf is attached. > All our workstations stopped working. If I change the computer name, > switch to workgroup, then try to re-join the domain under a different > computer name, it works. Do you know what .tdb file machine information > is stored in. > Also I exported all information from the pdbedit backend using pdbedit > -e to an smbpasswd format and everything looked fine. All machine > accounts were listed. So I don't think it's the passdb.tdb. This smb.conf snippet looks telling: > passdb backend = smbpasswd > #passdb backend = smbpasswd unixsam > #passdb backend = smbpasswd tdbsam unixsam You said you "exported all information [...] to an smbpasswd format", but your comments suggest that you are actually expecting samba to read its passdb from passdb.tdb. The above snippet clearly shows that Samba is configured to look *only* at /etc/samba/smbpasswd, and not at /etc/samba/passdb.tdb. Could this be the source of the trouble? Can you confirm that *this* section of your smb.conf was the same before and after the upgrade to -4 -- in which case, I would suggest that an ill-fated config change took effect when smbd restarted at the time of the upgrade? Cheers, -- Steve Langasek postmodern programmer -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
