This is more of a curiosity then a real problem, I am just to lazy to reboot or log off my laptop.
I have connected to a network share on a Windows server with domain credentials from a non-domain Windows 7 machine, I didn't mark the option to remember the password.
The share is let's say \\10.10.10.10\folder
.
I have changed the password for that domain account in the meantime, and now when I try to access that share I get the following error:
Logon failure: unknown user name or bad password
I have tried the following on the client side:
- deleting cached credentials in Credential Manager
- running
net use delete
- running
net session \\ip.of.the.server /delete
gives me "A session does not exist with that computer name." - running
net use \\10.10.10.10\folder /u:DOMAIN\USER password
gives me "The command completed successfully.", but I still get the same unknown user name or bad password when trying to access the share from Windows Explorer - mapping the share as a network drive from GUI, but then I get
The network folder specified is currently mapped using a different user name and password.
To connect using a different user name and password, first disconnect any existing mappings to this network share. - running
net use
to see connections, I get that there are no connections in the list - killing
explorer.exe
and starting it again.
I have tried the following on the server side:
- going to Computer Management > Shared folders > Sessions to kill the session with my username
- rebooting the server
I have managed to access the share using the domain name instead of the IP address, but I am curios.
Does anybody know any way how to delete the cached credentials in this case? Where are credentials cached when you don't mark the remember password option when accessing the share, they are not shown in Credential Manager and there is no mapping shown when you run net use.
NOT FOR WINDOWS 10 (I am answer for WINDOWS 7)
To delete all network authentication
To view current network connection
IMPORTANT NOTE
I tested in Windows 7 SP1 64 Bits, 100% WORK
After run the command, you need to go to task manager delete the explorer.exe , then reopen the application again.
To open the application, go to RUN, enter explorer.exe
Now you are fully clear the connection information in the session.
I know this is old, but in case anyone reads this in the future....
The next time this occurs I have found the best way to get rid of the credentials is to open an elevated command prompt and type in:
then type in:
I tried it with both command individually and they do not work alone. You have to first remove the connection if it exists. Then remove the Kerberos authentication ticket from the machine. I had an incident like yours where the connection no longer existed but the Kerberos ticket had not expired yet, so when I went back in and had not logged off of the machine it would use my previously entered credentials. By purging the ticket it prompted for credentials again.
Go to the control panel -> User accounts -> click on your name -> to the left click on "credentials" (or manage your credentials). All the used network credentials will be there.
The following should do what you want.
This is a sign of bad client side cache and usually relates with netbios.
Try to restart the below list of services and if need, kill explorer, start the task manager and start it again via the task manager file->run entry, as explorer may also be caching things from those services.
I don't know exactly what is the failing service on your side, so you can try this this list, one at time to see if it works:
if it works, report back what was the service, so others can try it directly
good luck
Let's say your server name is BIGSERVER and your user account is bigjim. You already logged in once so you'll need to delete the cached credentials.
These are found in :
[Windows 8] Windows key > Control panel > User accounts > Manage your credentials > Windows credentials > Remove server credentials.
Now restart explorer.exe
Access your server from windows explorer using \BIGSERVER\bigjim
As user, use BIGSERVER\bigjim (remember to use capital letters)