Windows · Windows Server · medium · Security, BitLocker & identity

A network resource keeps refusing credentials that are correct

A stored credential is being offered instead of the one being typed, or two different credentials are being used against the same server at once.

What you see

A share or a site rejects a password that definitely works elsewhere, or "Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed".

What is actually wrong

Credential Manager holds an entry that takes priority over what is typed. Error 1219 specifically is Windows refusing to hold two sessions to the same server under different accounts — a genuine protocol restriction, not a bug.

Codes and articles

The user name or password is incorrect0x8007052E0x80070056multiple connections to a server1219

Fixes (2)

Clear the stored credential that is winning

PowerShell as the affected user10 minuteslow riskreversible

A password is refused that is known to be right.

List what is stored. The entry for that server is almost always here.
Command Prompt
```
cmdkey /list
```
Delete the specific entry.
Command Prompt
```
cmdkey /delete:fileserver01
```
Windows offers a stored credential before it prompts. When the stored one is stale, the prompt never appears and the failure looks like the password itself is wrong.
Check the Web Credentials tab in Credential Manager as well — browsers and Office store there and it is a separate list.
Command Prompt
```
control /name Microsoft.CredentialManager
```
Reconnect and let it prompt. Tick remember only once it is proven to work.

Confirm it workedThe resource opens with the correct credentials and reconnects after a restart.

PowerShell

cmdkey /list | Select-String fileserver01

If you need to undo itCredentials are re-created by the next successful connection.

Drop the existing session before opening another

Elevated Command Prompt10 minuteslow riskreversible

Error 1219 or the multiple-connections message.

See every session to that server, including the ones with no drive letter.
Command Prompt
```
net use
```
Disconnect them all.
Command Prompt
```
net use * /delete /y
```
The invisible sessions are the problem: a share opened once in Explorer holds a connection with no drive letter, and it still counts. Deleting only the mapped drives leaves the conflict in place.
Clear any stored credential for that server as above, then connect once with the account you intend to use.
Command Prompt
```
cmdkey /delete:fileserver01net use \\fileserver01\share /user:DOMAIN\user
```
If two different accounts genuinely have to reach the same server at once, use the IP for one and the name for the other — Windows treats them as different targets.

Confirm it workedBoth resources open with the intended accounts.

Command Prompt

net use

If you need to undo itMapped drives set to reconnect restore themselves at sign-in.

Related faults

Where this stops. This write-up was written and checked by hand. It says what each step changes, how to confirm it worked and how to reverse it, and anything destructive is flagged before you reach it. If it does not match what your machine is doing, search the Support Centre for the exact code or message — and when something needs a person, get in touch.