DelphiFAQ Home Search:

Credentials supplied conflict with an existing set of credentials


comments30 comments. Current rating: 5 stars (16 votes). Leave comments and/ or rate it.


This is not directly Delphi related but happens sometimes when setting up shared drives. In my case, I got this error message after installing SAMBA on a Linux box, then sharing a directory and the protecting this resource on the Linux side with an account.

I tried to access the shared resource from a Windows NT machine via Explorer or command line using NET USE - but kept getting this error message:
'Credentials supplied conflict with an existing set of credentials'

(On a Windows XP box this error did not occur.)


From Microsoft: 'Windows NT does not allow you to make multiple connections to a shared network server from the same workstation if you attempt to use more than one set of credentials.'

This was basically a long winded version of the error message. Not too helpful. I looked at my shares but could not see any mapped drives to that machine except the IPC entry.


At the command line, in a desperate attempt, I removed all shares to other machines with this trick:


It was an attempt because until now I didn't realize that the NET command accepts wildcards (*) for machine names.

After that I could connect just fine. I suppose booting the machine would have done the trick as well.

Another possiblity is to provide the TCP/IP address of the computer instead of the computer name when you make that second connection. If you were already using the IP number in the first place, try the machine name this time. That might save you from removing all your network shares.


You are on page 2 of 2, other pages: 1 [2]
2007-02-10, 05:18:14
Great TIp. Thanks a lot. - Temjen
2007-05-03, 04:20:10
Hrobky from Slovak Republic  
Some times you get this error msg even if there is nothing listed in the 'net use' list. The command 'net use * /delete' is also unuseable. I tried to restart and mount the drive before mounting anything else. Still getting the msg.

Your credentials depend on the first network mount you perform. Windows stores the persistent connections in registry. Check the key HKCU/Network. I've had the key empty and it still had not worked.
1. So I mapped a network drive (right click My computer -> map network drive) using IP address instead of computer name.
2. I set the share as persistent (reconnect at logon) and filled in the user name (connect using a different user name).
3. Now it was listed in the registry. Here I edited the RemotePath string value in <share name> key, so that it contained computer name (or whatever else - you can create new connections this way).
4. I restarted the computer and after logging in I was asked for the password for the share BEFORE any onther program (most likely explorer) could obtain the credentials.

Since now was the share working again (using sharename, not IP addr).

For fixing another user: you (as administrator) can substitute HKCU by any other local user key. If the user is not local, or you are on a domain, you can load user.dat from stored user profile as hive. regedt32.exe -> HKEY_USERS -> load hive -> user.dat file
2007-07-12, 19:49:08
anonymous from Indonesia  
A very useful tip.

Thanks A LOT..
2008-01-24, 22:13:58
anonymous from Australia  
Thanks Mate
It was of great help. Saved lot of my time breaking my head on other possiblities for this error.
2008-02-05, 03:21:30   (updated: 2008-02-05, 03:25:04)
anonymous from India  
Thanks for the solution.........I can able to open shared folder from another system now......
2008-04-03, 02:57:29 from India  
Thanks Budy
2008-05-13, 10:33:46
anonymous from Milwaukee, United States  
Yes, that 100% solved my issue. I had tried to browse for the Samba PDC from my Win2K server and the IPC$ share was being held open. Looks like this solution is the gift that keeps on giving.
2009-03-26, 21:46:30
anonymous from United Kingdom  
Wow it fixed same error message connecting to file server over VPN using UNC name. Since last successful connection password has changed and client (Win2000) rebooted many times. Surprised the 'connection' persists through reboots even though the actual VPN has not been connected to for many sessions!
2009-06-18, 14:11:48
anonymous from United States  
Error 1219 appeared because an initial attempt to run a network shared application failed. The error message dialog from the application on the mapped drive was obscured by other windows. As long as the error message was running, attempts to remap the drive letter to the shared application produced the error 1219.

Once I closed the error message from the initial attempt to run the mapped applictation, I was able to re-map the drive letter with the appropriate credentials. I hope this helps someone else.
2009-08-28, 12:53:55
Thanks Man!
2009-12-23, 06:45:48
Your solution is very good. It resolved my problem. Thanks
2012-04-23, 17:21:51
anonymous from United States  
This is the gift that keeps on giving. Over 6 years later this solved my problem. And don't you just love MS's unhelpful help.

2012-05-05, 12:25:13
Thank you, it solved my problem.
2012-12-07, 00:09:07
There is an easy workaround without downloading a utility or replacing your windows computer.

Connecting the same server with two different accounts can be circumvented when redefining the name of the server, so in this issue when you tried:

net use \\server\share 'userPassword' /DomainName:DomainUserID
The command completed successfully.

net use \\server\share 'DifferentuserPassword' /DomainName:DifferntDomainUserID
The credentials supplied conflict with an existing connection.

Fix it by:
net use \\\share 'DifferentuserPassword2' /DomainName:DifferntDomainUserID2
The command completed successfully.

And you can use the IP address and connect a third time:
net use \\\share 'DifferentuserPassword3' /DomainName:DifferntDomainUserID3

Do it forever until you run out of combinations, even if you exhaust your driver letters you still map to and access by the entire server and share name.
This works on any domain or network without a domain/directory

net use \\\share 'DifferentuserPassword4' /DomainName:DifferntDomainUserID4

net use \\\share 'DifferentuserPassword5' /DomainName:DifferntDomainUserID5

net use \\\share 'DifferentuserPassword6' /DomainName:DifferntDomainUserID6

net use \\\share 'DifferentuserPassword7' /DomainName:DifferntDomainUserID7
2013-06-18, 15:44:34
anonymous from United Kingdom  
You are on page 2 of 2, other pages: 1 [2]



NEW: Optional: Register   Login
Email address (not necessary):

Rate as
Hide my email when showing my comment.
Please notify me once a day about new comments on this topic.
Please provide a valid email address if you select this option, or post under a registered account.

Show city and country
Show country only
Hide my location
You can mark text as 'quoted' by putting [quote] .. [/quote] around it.
Please type in the code:

Please do not post inappropriate pictures. Inappropriate pictures include pictures of minors and nudity.
The owner of this web site reserves the right to delete such material.

photo Add a picture: