Visit for the latest news on SharePoint.

Sometimes Windows networking really does my head in. Not only does it take up to a minute to connect to a network resource that is literally sitting one meter away, it also has annoying limitations such as the one listed in the title of this article.
I have seen this message before and usually disconnecting a network drive would do the trick. This time however the message would just not go away.
After a couple of minutes of Googling I found the solution in the following command:
net use * /delete

Comments on: "multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed" (37)

  1. Thank you very much nice guy,you saved my office…

  2. Thank you for this.  I hit this wall–between the Good Book Google and you my network issues are being resolved.  Thx!

  3. Thanks, nice tip.

  4. Oh man, thank you so much!!!God bless you!!!

  5. Thanks very, very much for this simple but effective tip. I knew what area the problem was but I couldn\’t find the way to resolve it until I found this very easy solution.

  6. Thanks! I was worried this might harm my computer. I don\’t like typing "delete" anywhere into the command line, but it just deleted the old connections. This command cleared everything up. It did what you said it would. Thanks again!

  7. Shubham said:

    I have done the same thing but I am not able to access shared folders of my Win 2K3 server from a Win XP machine. Both machines are in same workgroup.Please help me out.

  8. Unknown said:

    I had about 10 connections, and only needed to delete one of them.  It was simple to do… like this…
    net use \\\\\\directory /delete
    – Scott

  9. Thanks…that was so easy…..worked perfectly for me!:-)deb

  10. Thanks,  it worked well 🙂

    wow, strong…

  12. Oh man, thank you so much!!! You just saved me a couple of hours searching for right answer!! Thanks a milion!

  13. Is it possible to add this to beginning of my startup script, so that is clears everything out before I map the drives? You need to press Y to continue, can that be automated?

  14. Kiattikorn said:

    Thank you It worked well>>

  15. Dimitris said:

    Create a .txt file and type in there..echo oncd\\.net use * /delete /YThat should work for you!

  16. Dimitris said:

    Sorry I forgot to tell you that at the end you have to rename the file from .txt to .cmd and put it at start up!

  17. Jonathan said:

    Hi folks, how do I utilize this script? I\’ve never done one before, and it\’s driving me crazy.

  18. Thanks!! Worked great.

  19. Ditto everyone below. Thanks!To those who don\’t know how to use this (IE people like Jonathan Josh), here are some steps:1. Go to \’Start\’, then \’Run…\’2. In the \’Run\’ dialog box, type "cmd". This will bring up the command prompt.3. Inside the command prompt, type what was written above: "net use * /delete"4. It\’ll ask you if you wanna proceed; click yes. Doing so will wipe all mapped drives from your system, but getting them back is a fairly easy process. Much easier than trying to find a different solution to the "shared resource by same user" error.Thanks again!-K

  20. The question is why? why? why? does this limitation exist. It’s certainly has never existed in Unix. The problem is that disconnecting a single drive doesn’t always work. Disconnecting all the connections does work, but this is not an acceptable solution, especially on a so-called server.

  21. Thanks . Its working fine………….

  22. Cool. Thanks a lot for your tip!

  23. Thank you very much…
    i need this information and it’s work !!!!!!

  24. Thanks…………………

  25. thanks. good tip

  26. good article… thank you so much….

  27. Anonymous said:

    Totally helpful!!!

  28. much appreciated

  29. Thaaaank you!!!!!
    Greetings from Serbia!

  30. Don’t know what can I say that hasn’t been told yet but THANKS!!! It’s 2:00am, and I can finally move on in my installation.

  31. Thanks! This is helpful..

  32. THanks a lot!!

  33. I was stumped by this error message for a while. In my case, I was logged in as a network domain user, but had an application that was authenticating a local user on the machine.

    All I needed to do was close a few Windows Explorer windows…which were displaying network drives…and the error went away. Thank you very much for sharing. Your posting saved me.

  34. tried it on Windows 7 (input the command in cmd). got a confirmation message, but it doesn’t work; apparently it’s still the same user connected to the nas network and the same damn error message appears. tried the command again, and this time no entries were listed, but apparently that doesn’t reflect what’s actually the case

  35. oh wait, something just happened. it looks like it finally logged into the account it was trying to log into before… wtf microsoft

  36. You are a life saver….I spent couple of hours figuring this out without any luck and looks like this does the trick. Thanks again.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Tag Cloud

%d bloggers like this: