Multiple connections to a server or shared resource error (4033893)

Chat now with support

Get Live Help
Complete Registration

Sign In

Request Pricing

Contact Sales

Return

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Title

Multiple connections to a server or shared resource error
Description

Customers running vRanger 7.x on Server 2012 or Windows 8 receives the following error:
"Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again."
First observed when using a san running SMB 2.1 service (Initially observed with the EMC Isilon SAN appliance).
This occurs when a user tries to use a common hostname with when setting up a repository. The SAN itself may have multiple IP addresses that all resolve to a common hostname.
Using the Net Use in a CMD prompt shows no active connections to shares.
Cause

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.
Resolution
To resolve this issue, 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.
Microsoft offers a potential workaround by using one of these two 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:
Set-SmbClientConfiguration -RequireSecuritySignature $true
--Disable "Secure Negotiate" on the client
Alternatively, you can disable the Secure Negotiate option by using PowerShell on a Windows Server 2012 or Windows 8 client. To do this, run the following command:
```
Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" RequireSecureNegotiate 
```
More information can be found by going to the following link:
http://support.microsoft.com/kb/2686098

Feedback Submitted

Did this article solve an issue for you?

Select Rating

Request a KB Article

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

Multiple connections to a server or shared resource error (4033893)

Title

Description

Cause

Resolution

Leave a Comment