I have also discovered from answer that Windows will clear the old network credentials when there is a new login attempt. Then try your net use \\somemachine\someshare /user:someuser command again to get re-prompted for credentials. Locate the service named "Workstation".Tap Windows key, type services, press Enter.If you don't like command line stuff, you can alternatively restart the Workstation service by going to Services directly: This has the added bonus that although you will disconnect any existing shares, they won't be forgotten as they would if you had deleted them with something like net use * /d. So instead I suggest fixing the problem without rebooting by doing this: net stop workstation Disconnect all previous connections to the server or shared resource and try again. Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. These policies help protect your PC from unsafe or malicious devices on the network. You can't access this shared folder because your organization's security policies block unauthenticated guest access. Furthermore, if you have cached credentials to the network share, then when you re-establish the connection you may find yourself fighting one of these errors: You could, of course, remove your connection by doing net use \\somemachine\someshare /dīut you probably want to re-connect eventually too. Just browsing to the server in the explorer, without even connecting a share does count, and prevents you from using another credential to log onto that server, unless you disguise the name.Īccording to Microsoft, this is a feature. You remove a share my either right-clicking it, or net use x: /deleteīut: This does not remove your client's presumed connection to the server. Even works to connect to, say c$, on your own computer with admin rights. Incredibly useful when you try to debug user permission problems from the user's computer. This way, you can even connect twice to the same share, with different credentials. Net use * \\x.y.z.z'\mysharename /user:mydomain\theotheruser * /persistent:no Personally, I do this in the command line: net use * \\myservername\mysharename /user:mydomain\theotheruser * /persistent:no You can circumvent this by using the server´s IP Address instead of the Servername. This interception happens on the client side, not the server side. Windows tries to prevent logging on to the same server with different credentials at the same time, for some obscure "security reason".
0 kommentar(er)
