I recently upgraded a fileserver running Slackware 12.2 (Samba 3.2.x) to 13.1 (64 bit) but haven't been able to authenticate or access shares from any of the Windows PCs on the local network post-upgrade. I'm using the same smb.conf as before. All the Windows boxes are running XP SP3; they can see the server within the local network, but can't get past the authentication dialog. I'm sure this is most likely a simple matter of needing a new line in the smb configuration file, but I haven't been able to pin down any changes between the 3.2 and 3.5 Samba series that would require additional parameters. Thanks in advance for your help; my smb.conf is below:

Since you're using valid users = @weaver, and @weaveradmin, did you setup and add the extra users to those groups?

I always run testparm to validate my smb.conf.

I had to recreate the Samba passwords.

Yes--all users have been added and made members of appropriate groups. I also ran testparm, which did not raise any alerts.

How do you mean? The passdb.tdb and secrets.tbd files stored in /etc/samba/private were created new with this installation. Since I went from a 32bit version of slackware to a 64 bit, I wiped clean the entire filesystem, sans /home, prior to the install.

smbpasswd

What I meant was that the following solved a similar problem for me:

smbpasswd -a user

I upgraded 64-bit Slackware 13.0 to 13.1 without wiping anything.

Thanks all for the timely replies. Totally forgot that if you add users after Samba creates the .tdb files that you also have to run smbpasswd. D'oh! Problem solved.