This problem is caused by the "Secure Negotiate" feature that was added to SMB 3.0 for Windows Server 2012 and Windows 8. This feature depends upon the correct signing of error responses by all SMBv2 servers, including servers that support only protocol versions 2.0 and 2.1. I think Dynamox provided a solution.
I enabled the EnableSecuritySignature and RequireSecuritySignature values in the Windows registry and now typing \\192.168.2.230 via Windows Explorer I can see a shared folder like this "\!" and I can't access.
I enabled the EnableSecuritySignature and RequireSecuritySignature values in the Windows registry and now typing \\192.168.2.230 via Windows Explorer I can see a shared folder like this "\!" and I can't access.
dynamox
9 Legend
•
20.4K Posts
0
February 27th, 2014 08:00
try disabling SMB Signing on Win2k12 server
Jeffey1
4 Operator
•
2.8K Posts
0
February 28th, 2014 00:00
I noticed the customer has encounter the same error messages when using windows2012 connect to Isilon (link: http://social.technet.microsoft.com/Forums/windowsserver/en-US/78d2fb4d-267f-4c7b-9766-7a249b8c71cb/ws2012w8-cant-connect-to-isilon-nas-network-error-1208-helpany-ideas?forum=winserver8gen)
This problem is caused by the "Secure Negotiate" feature that was added to SMB 3.0 for Windows Server 2012 and Windows 8. This feature depends upon the correct signing of error responses by all SMBv2 servers, including servers that support only protocol versions 2.0 and 2.1. I think Dynamox provided a solution.
Fabio_Nanni
1 Rookie
•
70 Posts
0
February 28th, 2014 02:00
I enabled the EnableSecuritySignature and RequireSecuritySignature values in the Windows registry and now typing \\192.168.2.230 via Windows Explorer I can see a shared folder like this "\!" and I can't access.
What is that share?
Fabio_Nanni
1 Rookie
•
70 Posts
0
February 28th, 2014 02:00
How can I check which SMB protocol is enabled on the NAS?
Fabio_Nanni
1 Rookie
•
70 Posts
0
February 28th, 2014 07:00
I found the solution. I modified the following key:
Set-ItemProperty -Path “HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters” RequireSecureNegotiate -Value 0 -Force
Now it works.
Fabio_Nanni
1 Rookie
•
70 Posts
0
February 28th, 2014 07:00
I enabled the EnableSecuritySignature and RequireSecuritySignature values in the Windows registry and now typing \\192.168.2.230 via Windows Explorer I can see a shared folder like this "\!" and I can't access.
dynamox
9 Legend
•
20.4K Posts
0
February 28th, 2014 12:00
and that command disable secure signing