Multiple connections error
up vote
1
down vote
favorite
Trying to access admin$ share on remote machine, I get this 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.
However, net use reports no entries:
C:UsersXXXX>net use
New connections will be remembered.
There are no entries in the list.
Can it be that admin$ doesn't exists on remote machine?
windows networking
add a comment |
up vote
1
down vote
favorite
Trying to access admin$ share on remote machine, I get this 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.
However, net use reports no entries:
C:UsersXXXX>net use
New connections will be remembered.
There are no entries in the list.
Can it be that admin$ doesn't exists on remote machine?
windows networking
Have you tried rebooting the remote machine?
– jftuga
Sep 8 '11 at 18:39
@jftuga: I think it is "Have you tried turning it off and on again?"
– grawity
Sep 8 '11 at 20:33
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Trying to access admin$ share on remote machine, I get this 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.
However, net use reports no entries:
C:UsersXXXX>net use
New connections will be remembered.
There are no entries in the list.
Can it be that admin$ doesn't exists on remote machine?
windows networking
Trying to access admin$ share on remote machine, I get this 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.
However, net use reports no entries:
C:UsersXXXX>net use
New connections will be remembered.
There are no entries in the list.
Can it be that admin$ doesn't exists on remote machine?
windows networking
windows networking
asked Sep 8 '11 at 18:15
Veehmot
1629
1629
Have you tried rebooting the remote machine?
– jftuga
Sep 8 '11 at 18:39
@jftuga: I think it is "Have you tried turning it off and on again?"
– grawity
Sep 8 '11 at 20:33
add a comment |
Have you tried rebooting the remote machine?
– jftuga
Sep 8 '11 at 18:39
@jftuga: I think it is "Have you tried turning it off and on again?"
– grawity
Sep 8 '11 at 20:33
Have you tried rebooting the remote machine?
– jftuga
Sep 8 '11 at 18:39
Have you tried rebooting the remote machine?
– jftuga
Sep 8 '11 at 18:39
@jftuga: I think it is "Have you tried turning it off and on again?"
– grawity
Sep 8 '11 at 20:33
@jftuga: I think it is "Have you tried turning it off and on again?"
– grawity
Sep 8 '11 at 20:33
add a comment |
2 Answers
2
active
oldest
votes
up vote
3
down vote
accepted
If a share does not exist, the server would return "Network name not found". What you are getting now means exactly that: there is another active connection.
It seems that net use only reports explicitly opened connections (net use \servershare
or mapped drives through GUI), but not implicit ones (established by simply opening a file or pipe). Use netstat
to see if there are any active SMB connections, and check with Process Explorer for processes that hold open handles to files on network shares.
I tried TCPView and you are right, it has a connection established. The remote port is 445 (NetBios I think) and the process is System, so I can't close it. How to close a NetBios connection withoutnet use * /d
?
– Veehmot
Sep 8 '11 at 20:20
@Veehmot: Close any open files that are using the connection, and it will (should) go away within seconds. Again, Process Explorer's search function should help.
– grawity
Sep 8 '11 at 20:32
Nevermind, I used Right Click -> Close Connection and it works fine now. Thanks!
– Veehmot
Sep 8 '11 at 20:37
add a comment |
up vote
0
down vote
Again i struggle with this problem...
There is lots of variations of this question across stackexchande sites...
So list of ways to deal with this:
- "Credential manager" to clean old credentials
- "net use" to list, and "net use * /delete" to remove everything
- netstat for debugging (thanks @grawity)
- connect to server by ip instead of it's name
Also, there is this feature, when Windows Explorer first uses local user credentials, allowing to enter correct credentials only if local credentials fail. This can give you quite a headache when server has that user or guest access, but you need to use another username.
UPD.
In my cause this behavior was caused by Windows update + legacy Group policy "Enable insecure guest logons". But without this group policy, no connections at all was possible to that server.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
If a share does not exist, the server would return "Network name not found". What you are getting now means exactly that: there is another active connection.
It seems that net use only reports explicitly opened connections (net use \servershare
or mapped drives through GUI), but not implicit ones (established by simply opening a file or pipe). Use netstat
to see if there are any active SMB connections, and check with Process Explorer for processes that hold open handles to files on network shares.
I tried TCPView and you are right, it has a connection established. The remote port is 445 (NetBios I think) and the process is System, so I can't close it. How to close a NetBios connection withoutnet use * /d
?
– Veehmot
Sep 8 '11 at 20:20
@Veehmot: Close any open files that are using the connection, and it will (should) go away within seconds. Again, Process Explorer's search function should help.
– grawity
Sep 8 '11 at 20:32
Nevermind, I used Right Click -> Close Connection and it works fine now. Thanks!
– Veehmot
Sep 8 '11 at 20:37
add a comment |
up vote
3
down vote
accepted
If a share does not exist, the server would return "Network name not found". What you are getting now means exactly that: there is another active connection.
It seems that net use only reports explicitly opened connections (net use \servershare
or mapped drives through GUI), but not implicit ones (established by simply opening a file or pipe). Use netstat
to see if there are any active SMB connections, and check with Process Explorer for processes that hold open handles to files on network shares.
I tried TCPView and you are right, it has a connection established. The remote port is 445 (NetBios I think) and the process is System, so I can't close it. How to close a NetBios connection withoutnet use * /d
?
– Veehmot
Sep 8 '11 at 20:20
@Veehmot: Close any open files that are using the connection, and it will (should) go away within seconds. Again, Process Explorer's search function should help.
– grawity
Sep 8 '11 at 20:32
Nevermind, I used Right Click -> Close Connection and it works fine now. Thanks!
– Veehmot
Sep 8 '11 at 20:37
add a comment |
up vote
3
down vote
accepted
up vote
3
down vote
accepted
If a share does not exist, the server would return "Network name not found". What you are getting now means exactly that: there is another active connection.
It seems that net use only reports explicitly opened connections (net use \servershare
or mapped drives through GUI), but not implicit ones (established by simply opening a file or pipe). Use netstat
to see if there are any active SMB connections, and check with Process Explorer for processes that hold open handles to files on network shares.
If a share does not exist, the server would return "Network name not found". What you are getting now means exactly that: there is another active connection.
It seems that net use only reports explicitly opened connections (net use \servershare
or mapped drives through GUI), but not implicit ones (established by simply opening a file or pipe). Use netstat
to see if there are any active SMB connections, and check with Process Explorer for processes that hold open handles to files on network shares.
answered Sep 8 '11 at 18:37
grawity
228k35481540
228k35481540
I tried TCPView and you are right, it has a connection established. The remote port is 445 (NetBios I think) and the process is System, so I can't close it. How to close a NetBios connection withoutnet use * /d
?
– Veehmot
Sep 8 '11 at 20:20
@Veehmot: Close any open files that are using the connection, and it will (should) go away within seconds. Again, Process Explorer's search function should help.
– grawity
Sep 8 '11 at 20:32
Nevermind, I used Right Click -> Close Connection and it works fine now. Thanks!
– Veehmot
Sep 8 '11 at 20:37
add a comment |
I tried TCPView and you are right, it has a connection established. The remote port is 445 (NetBios I think) and the process is System, so I can't close it. How to close a NetBios connection withoutnet use * /d
?
– Veehmot
Sep 8 '11 at 20:20
@Veehmot: Close any open files that are using the connection, and it will (should) go away within seconds. Again, Process Explorer's search function should help.
– grawity
Sep 8 '11 at 20:32
Nevermind, I used Right Click -> Close Connection and it works fine now. Thanks!
– Veehmot
Sep 8 '11 at 20:37
I tried TCPView and you are right, it has a connection established. The remote port is 445 (NetBios I think) and the process is System, so I can't close it. How to close a NetBios connection without
net use * /d
?– Veehmot
Sep 8 '11 at 20:20
I tried TCPView and you are right, it has a connection established. The remote port is 445 (NetBios I think) and the process is System, so I can't close it. How to close a NetBios connection without
net use * /d
?– Veehmot
Sep 8 '11 at 20:20
@Veehmot: Close any open files that are using the connection, and it will (should) go away within seconds. Again, Process Explorer's search function should help.
– grawity
Sep 8 '11 at 20:32
@Veehmot: Close any open files that are using the connection, and it will (should) go away within seconds. Again, Process Explorer's search function should help.
– grawity
Sep 8 '11 at 20:32
Nevermind, I used Right Click -> Close Connection and it works fine now. Thanks!
– Veehmot
Sep 8 '11 at 20:37
Nevermind, I used Right Click -> Close Connection and it works fine now. Thanks!
– Veehmot
Sep 8 '11 at 20:37
add a comment |
up vote
0
down vote
Again i struggle with this problem...
There is lots of variations of this question across stackexchande sites...
So list of ways to deal with this:
- "Credential manager" to clean old credentials
- "net use" to list, and "net use * /delete" to remove everything
- netstat for debugging (thanks @grawity)
- connect to server by ip instead of it's name
Also, there is this feature, when Windows Explorer first uses local user credentials, allowing to enter correct credentials only if local credentials fail. This can give you quite a headache when server has that user or guest access, but you need to use another username.
UPD.
In my cause this behavior was caused by Windows update + legacy Group policy "Enable insecure guest logons". But without this group policy, no connections at all was possible to that server.
add a comment |
up vote
0
down vote
Again i struggle with this problem...
There is lots of variations of this question across stackexchande sites...
So list of ways to deal with this:
- "Credential manager" to clean old credentials
- "net use" to list, and "net use * /delete" to remove everything
- netstat for debugging (thanks @grawity)
- connect to server by ip instead of it's name
Also, there is this feature, when Windows Explorer first uses local user credentials, allowing to enter correct credentials only if local credentials fail. This can give you quite a headache when server has that user or guest access, but you need to use another username.
UPD.
In my cause this behavior was caused by Windows update + legacy Group policy "Enable insecure guest logons". But without this group policy, no connections at all was possible to that server.
add a comment |
up vote
0
down vote
up vote
0
down vote
Again i struggle with this problem...
There is lots of variations of this question across stackexchande sites...
So list of ways to deal with this:
- "Credential manager" to clean old credentials
- "net use" to list, and "net use * /delete" to remove everything
- netstat for debugging (thanks @grawity)
- connect to server by ip instead of it's name
Also, there is this feature, when Windows Explorer first uses local user credentials, allowing to enter correct credentials only if local credentials fail. This can give you quite a headache when server has that user or guest access, but you need to use another username.
UPD.
In my cause this behavior was caused by Windows update + legacy Group policy "Enable insecure guest logons". But without this group policy, no connections at all was possible to that server.
Again i struggle with this problem...
There is lots of variations of this question across stackexchande sites...
So list of ways to deal with this:
- "Credential manager" to clean old credentials
- "net use" to list, and "net use * /delete" to remove everything
- netstat for debugging (thanks @grawity)
- connect to server by ip instead of it's name
Also, there is this feature, when Windows Explorer first uses local user credentials, allowing to enter correct credentials only if local credentials fail. This can give you quite a headache when server has that user or guest access, but you need to use another username.
UPD.
In my cause this behavior was caused by Windows update + legacy Group policy "Enable insecure guest logons". But without this group policy, no connections at all was possible to that server.
edited Nov 20 at 10:57
answered Nov 20 at 9:06
Andrei
1385
1385
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f333431%2fmultiple-connections-error%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you tried rebooting the remote machine?
– jftuga
Sep 8 '11 at 18:39
@jftuga: I think it is "Have you tried turning it off and on again?"
– grawity
Sep 8 '11 at 20:33