[Samba] RESOLVED: HELP: smb 3.6.20 and 3.6.21 broken with Win 8.1
Nulty, Helen P
hnulty at email.unc.edu
Tue Dec 3 08:59:25 MST 2013
The setting that fixed this issue for us was adding the following to our smb.conf:
Server signing = yes
We are now able to delay our implementation of samba 4.1 for the short term.
From: Marc Muehlfeld [mailto:samba at marc-muehlfeld.de]
Sent: Monday, December 02, 2013 2:42 PM
To: Nulty, Helen P; samba at lists.samba.org
Cc: Hill, Jennifer Caitlyn
Subject: Re: [Samba] HELP: smb 3.6.20 and 3.6.21 broken with Win 8.1
Am 02.12.2013 19:33, schrieb Nulty, Helen P:
> # smbd -V
> Version 3.6.20
> We have tried 3.6.21 on another server with same result.
Can you try 4.0 or 4.1?
The 3.6 series is meanwhile out of maintainance and in security-fixes-only mode. So if it's a bug, there's not a big chance to get this fixed. But 4.0 and 4.1 bring very much new changes and improvements and maybe the problem is already gone/fixed.
As 4 is the next release after 3, it isn't a big thing to upgrade (it's like switching from 3.5.x to 3.6.x).
In my test environment I have a 4.1.0 server (but without DFS) and 8.1 and this runs fine. And in production DFS with 4.1.0, but with Win7, what also works good.
But if the problem is around DFS/Win8.1 and still exists in 4.1, then you can open a bug report, add your smb.conf and a level 10 debug logfile containing the try to access the share.
More information about the samba