Access the network share again via name or IP, whichever you haven't already used.
If you connected to \\192.168.2.10\
with the wrong user you can try again once by using the server name instead. If you open \\Server\
you'll be prompted for your credentials again. From then on you'll have two open sessions to the same server but with different users. They seem to last until those logins expire which is potentially until the next logout.
Because of this you need to make sure that you're using the right path from now on! if you needed to login to an account with higher permissions to run a backup, make sure your backup tool now works with \Server[path]` and not the IP.
As far as I know this is the workaround that requires the least amount of effort. It's convenient when you want to avoid the hassle of logging in again or mapping a network drive.
12'net use' worked! The command 'net use \SERVER * /user:username' works to change the credentials for the share.
Thanks! – Tim – 2010-03-25T03:31:00.173
1Tried with
*
"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." Tried with\share
, says "The command completed successfully." but I still can't access the share. – Mark Jeronimus – 2016-02-14T10:05:12.483@tim That solution worked perfectly for me. I had a situation where I renamed my user on Synology NAS to make it align with my Windows user, but the home directory wouldn't show up, even after rebooting both server and client. I removed all old shares, and then executed
net use \\SERVER * /user:username
. Entered my password successfully and suddenly all my shares popped up. I should add that no drive letters were assigned, contrary to what SamB implies. Precisely the behaviour I expected. =) – paddy – 2016-07-06T09:04:39.9801@Tim M: Actually, it seems to work better as
net use \\SERVER\SHARE ...
-- that is, without the asterisk (and with a sharename, but I assume you used one when you actually ran it ;-). The asterisk causes a drive letter to be assigned; do this too many times and you'll run out! – SamB – 2010-07-04T20:23:25.110uh... where is this "link to Connect"? I don't see it when I right click on the share, and the Windows 7 Explorer doesn't have a nice menu structure that I can search in. – Michael – 2019-04-09T19:22:53.433
I have the same problem, but when doing it I get an error
System error 1326 has occurred.
andLogon failure: unknown user name or bad password.
but I know the username and passwor dare correct – Petah – 2011-05-17T03:50:27.983