We are running into this with Windows 10 and 8.3.2P6 CIFS Setup. The powershell command for Windows 10 secure negotation no longer works in Windows 10. All our computers are running ver 1511. We did turn on SMB signing on the Netapp CIFS SVM. We also tried all of the registry settings mentioned earlier.
Netapp don’t yet support win10 (hey it’s only been around 12 months in beta, you have to give these guys time)
You can’t cripple the SMB3 requirement in win 10, like you can in win8 and server 2012 – that I think is the core issue – the reg value is explicitly rejected by win 10, the reg value I am talking about is below – you can create any other value in that key, for example ‘bacon’ and set it to a value of 1, but not requiresecurenegotiate it gets rejected
After some more personal digging around (my support ticket was getting nowhere fast) I have managed to successfully browse CIFS shares on my snapmirror filer at our DC.
To do this I had to enable cifs signing and bounce the cifs service.
FILER> cifs terminate
CIFS local server is shutting down...
CIFS local server has shut down... FILER> options cifs.signing.enable on FILER> cifs restart CIFS local server is running. Can't set cifs branchcache server secret.
This filer is running 8.1.4P1 7-Mode
This weekend we have a full power shutdown at our production site so I will try this on power up. It's so hard to get the users to close down their connections!!!!
One thing I did notice though. The filer does not show the W10 client using security signatures - output from cifs sessions -t
Using domain authentication. Domain type is Windows 2000. Root volume language is not set. Use vol lang. Number of WINS servers: 0 Total CIFS sessions: 1 CIFS open shares: 1 CIFS open files: 0 CIFS locks: 3 CIFS credentials: 1 IPv4 CIFS sessions: 1 IPv6 CIFS sessions: 0 Cumulative IPv4 CIFS sessions: 26383 Cumulative IPv6 CIFS sessions: 0 CIFS sessions using security signatures: 0
Will post results from production environment after the weekend