LinuxQuestions.org - [SOLVED] Can't connect to Samba shares after 12.2-->13.1 upgrade (Samba 3.2.x-->3.5.2)

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Can't connect to Samba shares after 12.2-->13.1 upgrade (Samba 3.2.x-->3.5.2) (https://www.linuxquestions.org/questions/slackware-14/cant-connect-to-samba-shares-after-12-2-13-1-upgrade-samba-3-2-x-3-5-2-a-812693/)

Can't connect to Samba shares after 12.2-->13.1 upgrade (Samba 3.2.x-->3.5.2)

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:

Quote:

[global]
workgroup = WEAVER
server string = slackserver
security = user
max log size = 50
passdb backend = tdbsam
encrypt passwords = yes

[homes]
comment = home directories
browseable = no
writeable = yes

[weaver]
comment = weaver
path = /home/weaver
valid users = @weaver
writeable = yes
public = no
create mask = 0660
directory mask = 0770

[weaveradmin]
comment = weaveradmin
path = /home/weaveradmin
valid users = @weaveradmin
writeable = yes
public = no
create mask = 0660
directory mask = 0770

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.

Quote:

Originally Posted by nakedlunch (Post 3995577)

I had to recreate the Samba passwords.

Quote:

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.

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

Quote:

I had to recreate the Samba passwords.

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.

Quote:

Originally Posted by nakedlunch (Post 3995781)

Quote:

Originally Posted by gezley (Post 3995742)

I had to recreate the Samba passwords.

smbpasswd

Quote:

Originally Posted by nakedlunch (Post 3995781)

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.

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.