After upgrade to Tumbleweed, Windows7 and Ubuntu12.04 can not connect to samba shares

English Network/Internet
1

A machine with version 13.1 was used as a samba server/FTP server. Clients were Windows7, Ubuntu12.04 (redobackup live-CD) and Tumbleweed machines. All worked well.
Upgrade of the samba server was delayed because of pam_userdb to pam_pwdfile transfer-problems with vsftpd.
These have been solved and the samba server now has been upgraded to Tumbleweed as O/S.
The smb.conf file has been copied and not changed.

Since the upgrade, Tumbleweed clients can connect to the samba shares as before (via mount.cifs and in Dolphin), but Windows7 machines (in explorer and command line) and machines using redobackup (Ubuntu 12.04, with mount.cifs) get errors (password incorrect).
The samba user has it’s password set with smbpasswd -a smbuser.

I assume that the security level on the samba server now is too high for Windows7 and Ubuntu12.04, but I don’t know how to fix it.

smb.conf is:
#start of smb.conf

[global]
workgroup = dci-electronics
usershare allow guests = No
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
domain logons = NO
domain master = NO
security = auto
netbios name = dci-lfs-02
printcap name = /dev/null
load printers = no
ldap admin dn =
passdb backend = smbpasswd
wins server =
wins support = No

[images]
comment = hardisk images client pcs
path = /images
writeable = yes
create mask = 0664
guest ok = yes
force user = smbuser
inherit acls = yes
browseable = yes

[images2]
comment = oude hardisk images client pcs
path = /images2
writeable = no
guest ok = No
force user = smbuser
inherit acls = yes
browseable = yes
read only = Yes

[LMW]
comment = LMW documentatie
path = /smbdata/LMW
writeable = yes
create mask = 0664
guest ok = yes
force user = smbuser
inherit acls = yes
browseable = yes

#end of smb.conf

The mount command used is (Tumbleweed and Ubuntu)
mount.cifs //10.0.0.x/sharename dir -o username=smbuser,password=“xxx”
the net use command used is (Windows)
net use x: \10.0.0.x\sharename /user:smbuser

2

I really don’t know, but here are some random thoughts.

Is smbuser a Linux user on the Tumbleweed server?
(I think you will say “yes”)

Security might drop if you do this
Try this:

security = user

And then redo this:

smbpasswd -a smbuser

These are superfluous I hope:

wins server =
wins support = No

But just in case they are doing something, make them like this

##wins server =
##wins support = No

Then reboot Linux and then reboot Win 7.

Check that the daemons are running. I think they are or some things would already be not working, but just check anyway, these comnads.

systemctl status nmb.service
systemctl status smb.service
3

Another passing thought:

This: “force user = smbuser” would imply that the ownerships of the directories “images” and “images2” and “smbdata/LWW” have owner user=smbuser (and I suppose group=users)

4

Tumbleweed switched to SMB3 by default.

Try defining the client min/max protocol in smb.conf (under [global] )

client min protocol = SMB2 
client max protocol = SMB3

Restart smb.

5

Is smbuser a Linux user on the Tumbleweed server?

yes, it is.

Security might drop if you do this
Try this:

security = user

And then redo this:

smbpasswd -a smbuser

No luck.

These are superfluous I hope:

wins server =
wins support = No

But just in case they are doing something, make them like this

##wins server =
##wins support = No

Then reboot Linux and then reboot Win 7.

No change (these lines are leftovers from years back and can probably be removed safely).

Check that the daemons are running. I think they are or some things would already be not working, but just check anyway, these comnads.

systemctl status nmb.service
systemctl status smb.service

[/QUOTE]

These are running fine (and samba connections work fine from clients with Tumbleweed).

6

That is correct, smbuser is the owner of the shared directories.

7

No change. Connection from Windows7 not possible (Invalid password, error 86) and from Dolphin on Tumbleweed effortlessly.

8

I wonder if win 7 has an error. Internet says it’s a real issue and fixable, many instances in google search. For example this: http://www.solvusoft.com/en/errors/windows-system-error-codes/microsoft-corporation/windows-operating-system/error-86-error-invalid-password/

Do you have another windows computer you could attach to the LAN, to see if that other windows has a problem?

9

Anything in a logfile? Or in the journal ?

10

Yes, succeeded! This difference with yesterday’s no-luck was a reboot of the Windows client.
Thanks!

11

The solution was in the server, as the only changes (upgrade) were on the server. What I didn’t realise was that every simple change on the samba server needs the Windows client(s) to reboot.
Switching on another Windows computer, which then didn’t have the problem, made me realise this.
Thanks!

12

The log files (log.nmbd and log.smbd didn’t mention anything except that starting the services succeeded.
The problem has been solved since.
Thank you for your suggestions.

13

Good job. The good old windows reboot. Glad you found thge solution.