About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
The message reads: "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." It means the Windows session you are working in already has a connection to that server under one user name, and you have just asked for another under a different one. Find the existing connection with net use, remove it, and reconnect with the single account you want.
The fault is on the client side of the connection. The message comes from the client's own list of connections, and the password you typed may be perfectly correct.
What the error means
Microsoft lists this as system error 1219 (0x4C3), ERROR_SESSION_CREDENTIAL_CONFLICT, with exactly the text above. The text itself says what Windows wants: all previous connections to that server or shared resource disconnected, then the attempt repeated.
net use is the command that makes and removes these connections. Microsoft describes it as connecting "a computer to or disconnects a computer from a shared resource". Used without parameters it "retrieves a list of network connections", which is the list you need. The /user parameter "specifies a different user name with which the connection is made", which is one way a second user name arrives.
Two documented behaviours matter here. First, net use with /delete "cancels the specified network connection", and with an asterisk instead of a name "all network connections are canceled". Second, "you cannot disconnect from a shared directory if you use it as your current drive or an active process is using it." If a program is holding the share, the disconnect will fail and the conflict will stay.
The net use page cited is archived documentation for Windows Server 2012 R2 and earlier. The syntax given below is the syntax on that page; confirm it with net help use on your own system.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| A drive is mapped to the server under your normal account and a command now uses an admin or service account | 1219 on the second connection | net use lists a connection to the same server |
| A persistent mapping restored at sign-in | The conflict appears after every logon | net use lists the mapping again after each sign-in; Microsoft says persistent connections are restored at the next logon |
| A stored credential for the server name (a possibility; the cmdkey page documents only storing, listing and deleting) | An earlier connection used the stored user name, so a later /user: conflicts with it |
cmdkey /list shows an entry for the server |
| A script, scheduled task or service that connected earlier in the same session | 1219 only after the job runs | Run net use from the same session as the job |
| A program is using the share, so the old connection will not drop | The disconnect fails or the connection returns | Close the program, or find the process using the drive |
Prove the cause before changing anything
All of these only read.
On the client, in the session that shows the error, list the connections:
net use
Look for any entry whose remote name begins with the server in your failing command. Microsoft documents net use DeviceName for details of one connection. Write down the user name each connection used. If you cannot see it, the stored credentials are the next place to look.
List stored credentials:
cmdkey /list
Microsoft documents that /list "displays the list of stored user names and credentials", and that if no target name is given all are listed. cmdkey /list:server01 narrows it to one target.
On the file server, read the sessions it holds for that client. Get-SmbSession accepts -ClientComputerName and -ClientUserName:
Get-SmbSession -ClientComputerName <client IP address>
The cmdlet returns session identifiers, the client's address, the user name and the count of open files (NumOpens). Add | Select-Object -Property * to see more fields, such as SecondsIdle. A good result for a client that is working shows one user name. Two sessions with different user names from the same client confirm the conflict from the server side.
Check who the failing command is trying to use. A command such as net use \\fs01\share /user:CONTOSO\svc-reports names a second account; confirm it is the one you meant.
Fix
Choose the fix that matches what you found. Work from the narrowest to the broadest.
One conflicting mapping. Remove only that connection:
Disruptive step: net use f: /delete cancels the connection on drive F: for the current user. Any program or open file using F: loses access, and the unsaved data in it may be lost. To back out, remap the drive with net use f: \\server\share and the correct user name.
net use f: /delete
Every connection to the server. If there are several and you want a clean start:
Disruptive step: net use * /delete cancels all network connections for the session, not only the one that conflicts. Microsoft documents the asterisk as cancelling all of them. Drives and open files go with them. To back out, remap each connection from the list you saved earlier.
net use * /delete
A persistent mapping that returns at every sign-in. Microsoft says "Use /delete to remove persistent connections", and /persistent:no "does not save the connection being made or subsequent connections". Delete the mapping, then reconnect with persistence set to suit you.
Disruptive step: deleting a persistent mapping removes the drive from this user's sign-in for good, until it is made again. Impact: the drive letter disappears at every later sign-in and anything using it fails. Back-out: recreate it with net use <letter>: \\server\share /persistent:yes and the correct user name.
A stored credential that supplies the wrong user name.
Disruptive step: cmdkey /delete:server01 removes the stored user name and password for that target. Anything that relied on it will prompt for credentials or fail. To back out, add it again with cmdkey /add:server01 /user:<name>, which prompts for the password.
cmdkey /delete:server01
A program holding the connection. Close the program (or stop the scheduled task or service that owns it) and repeat the /delete. Microsoft's remark about active processes explains why the delete fails otherwise.
Disruptive step: closing a program loses its unsaved work, and stopping a scheduled task or service halts whatever that job does until it is started again. Back-out for a task or service: start it again; there is no way back for unsaved work, so have the user save first.
Decide which account should win. The error is a conflict, not a verdict on either account. Before you delete anything, decide which user name this session should use for this server. A person browsing folders needs their own account. A scheduled job needs its service account in its own session, not in a user's session. If both are needed on the same computer at the same time, run the second one in a separate Windows session, so each session holds one set of credentials for the server.
Reconnect with one account. Connect once, under the account you want, and prompt for the password rather than putting it in the command:
net use \\fs01\finance * /user:CONTOSO\jsmith
The syntax allows an asterisk where the password goes, and Microsoft documents that it "produces a prompt for the password". Pick the account that has the permission and use it for every connection to that server from this session.
Confirm the fix
Run net use again. The list should contain one entry for the server, or none if you only needed the new connection. Open the share and the folder your task needs. On the server, Get-SmbSession -ClientComputerName <client IP address> should show a single user name for that client.
Example (illustrative): on workstation ws14, user CONTOSO\jsmith has drive H: mapped to \\fs01\home. A help-desk technician signs in as jsmith and runs net use \\fs01\finance /user:CONTOSO\svc-reports, which returns system error 1219. net use shows the H: connection. On fs01, Get-SmbSession -ClientComputerName 10.0.20.14 | Select-Object -Property * shows a session for CONTOSO\jsmith with NumOpens of 4 and SecondsIdle of 5,400, which is 90 minutes. The technician saves the output, closes the document held open on H:, runs net use h: /delete, and reconnects \\fs01\finance as CONTOSO\svc-reports. The user's home drive is remapped afterwards.
What to watch afterwards
- If the error comes back at each sign-in, a persistent mapping or a login script is recreating the second connection. Settle on one account per server for each Windows session.
- Keep a short list of which service accounts reach which servers, so that a technician does not mix accounts in a user's session.
- Stored credentials accumulate. Check
cmdkey /liston shared and jump-host computers. - If drives show a red cross after sign-in instead of an error, the fault is a mapped drive that fails to reconnect at sign-in, which is a different problem.
Read next
Related articles you may want next.
- TroubleshootingSystem error 53 "The network path was not found": name, port 445 or the Server serviceSystem error 53 means the client could not reach the share. Check the server's name, TCP port 445, the Server service and the firewall at the other end, and the client's own TCP/IP NetBIOS Helper service. Prove each one in turn.Read article
- TroubleshootingMapped network drives show a red X after sign-in: idle disconnects, network timing and policyA red X on a mapped drive can mean an idle connection that reconnects when you open it, a drive mapped before the network was up, a program running elevated, or a Group Policy drive map clearing other drives. Prove which one before you change anything.Read article
- TroubleshootingSMB Signing Now Required: NAS and Old Client Access FailuresNAS share fails after Windows 11 24H2 or Server 2025? Tell signing (STATUS_INVALID_SIGNATURE) from blocked guest access, audit with SMBClient events, fix the device first.Read article
Risks and limits
These commands have not been run or lab-tested.
The pages cited document the error text, the /delete and /persistent parameters and the stored-credential commands. They do not describe whether connecting to the same server by a different name form (an IP address or an alias) avoids the conflict, so that is not covered here. Test that on a spare machine if you intend to rely on it.
Removing connections ends access for programs that use them. Run net use first to see what the session holds, and do it when you know what is open in that session. If the error reads "network path was not found" instead, the fault is system error 53, which is a different problem.
Sources
- System Error Codes (1000-1299) — Microsoft Learn, page dated 2025-07-14, accessed 18 November 2026
- Net use (Windows Server 2012 R2 and 2012) — Microsoft Learn, page dated 2016-08-31, accessed 18 November 2026
- cmdkey — Microsoft Learn, page dated 2024-11-01, accessed 18 November 2026
- Get-SmbSession — Microsoft Learn, date not shown, accessed 18 November 2026
This article was originally published on .