Windows 7 - Cached Network Share Credentials?

42,674

Solution 1

Just reverse your troubleshooting steps:

  1. Start > Credential Manager > Windows Credentials > Remove from vault
  2. Start > Run > cmd > net use * /delete

And voila! Network shared access succeeds with a different username.

Solution 2

I have the same problem but with a Linux server. I first thought it was a name lookup problem - DNS clashing with NetBios - the DNS had the domain name and the NetBios the workgroup. I spent a lot of time trying to find out what was going on and I'm still not sure. But ---- I cleared the credentials (credential manager) and then set up a mapped drive but ticking the Connect using different credentials box and then entering the correct credentials. Imdediately I could browse, view and connect to the shares on the linux box - even after removing the mapped drive. However after removing the share I had to enter the user and pass again. Still not sure I've got it. mikej

Share:
42,674

Related videos on Youtube

DrColossos
Author by

DrColossos

Updated on November 19, 2022

Comments

  • DrColossos
    DrColossos 12 months

    I have an issue in Windows 7 where I get the following error message when attempting to access an admin network share on a machine in another domain:

    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.

    Troubleshooting I've Done

    1. Start > Run > cmd > net use * /DELETE
    2. Start > Manage Windows Credentials > Deleted all credentials

    I still receive the same error until I reboot my machine. After I reboot, it works fine. However, I am able to log into the admin share if I hit it by its IP address.

    QUESTION

    My question is, is there somewhere else I should be looking for cached user credentials?

  • Admin
    Admin over 10 years
    Same problem but Windows Server 2003. Removed mapped drives and did exactly as you did, connect using "different" credentials (which were actually the same credentials) and it worked a treat. No idea why. Thanks!!