After a Windows Server 2012-based or Windows 8-based computer fails to connect to a third-party file server that supports the SMBv2 file protocol, you receive one of the following error messages or a similar error message, depending on how you access the third-party file server:
When you use a DIR command that has a UNC path:
When you run a NET USE command:
System error 2148073478 has occurred
When you try to browse to the UNC path:
An extended error has occurred
You may experience these errors in the following common scenarios:
A live migration of Hyper-V servers (running either Hyper-V Server 2012 or Windows Server 2012 and Window 8) fails. This occurs because the storage is required to be hosted on an SMB share.
You cannot map network drives to an SAN in a Window 8-Windows Server 2012 environment.
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. Some third-party file servers do not return a signed error response. Therefore, the connection fails.
To resolve this problem, contact the third-party file server vendor to request an update that enables the file server to support Windows Server 2012 and Windows 8 clients.
Warning We do not recommend that you disable the requirement for secure negotiate, as this reduces computer security. Disable secure negotiate only as a temporary troubleshooting measure. Do not leave secure negotiate disabled; instead, contact the third-party file server vendor and request an update that allows their file server to support Windows Server 2012 and Windows 8 clients correctly.
The ability to disable secure negotiate functionality may be removed in future operating systems.
To work around this problem, use either of the following methods:
Require signing on the third-party file server
To require signing on the SMB client or the SMB server, turn on the "RequireSecuritySignature" setting. See your vendor’s documentation for instructions to set the signing setting to "required" on the vendor’s SMB server.
You can enable signing by using PowerShell on a Windows Server 2012 or Windows 8 client. To do this, run the following command: