"The network folder specified is currently mapped using a different user name and password", when trying to connect to a drive remotely.

Anonymous

Original Title: 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.

I am trying to connect to a drive remotely. I have clicked to map to the drive, entered the name of the drive, entered the login name/password for the computer it resides on and then it give me this error message: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.

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

In Windows 7 Enterprise, I would like to point out that if you map \\server1\share1 as drive letter X using "user1" and "password1", then try to map \\server1\share2 (a different share) as drive letter Y using the same "user1" and "password1", and you click the "connect using different credentials" checkbox in the Map Network Drive dialog box and specify "user1" and "password1", you will get this INCORRECT ERROR MESSAGE that says "The network folder specified is currently mapped using a different user name and password".

The message is wrong because:

The network folder specified (share2 in my example) is not mapped at all, and
the server ("server1" in my example) is already mapped (to a different drive letter and different share) using the SAME userid and password.

The error message is wrong on two counts!

This baffled me for a while until I realized that once you have mapped to "server1" using those credentials, you can map to different shares on the same server without re-specifying the credentials. This is NOT CLEAR from the "Map Network Drives" dialog box, which leads to users (like me, and I'm a programmer by trade) trying to enter the credentials again and getting this incorrect error message.

David Walker

0 comments

52 additional answers

Anonymous

2013-10-30T17:04:10+00:00

Yes, this is exactly what happened to me. Too bad their is no real solution. I would have expected a patch/update to fix this issue by now, more than three years later. In summary, its not possible to connect to multiple shares on a server from a single client, unless all connections formed are with the same user/credentials.

net use /delete did not help, even when the net list was empty.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2013-07-15T21:11:07+00:00

I checked the registry location you specified, and the network share is not there. Hmm, as you said, it appears that Windows 7 is treating a favorite, which is just a link (not a mapped drive) the same as a mapped drive. Interesting.... It's OK because I can now access it via the link, but it's a little confusing that it's behaving this way. Thanks for your help!
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2013-07-15T20:51:33+00:00

hmm, could be the culprit. Otherwise another location for mapped drive information is stored under this key in the registry:

HKEY_CURRENT_USER\Network\
Was this answer helpful?

3 people found this answer helpful.

0 comments No comments
Anonymous

2013-07-15T20:40:54+00:00

However, I just discovered something that may explain this. Under Favorites, I just found that my earlier attempt to add this share as a Favorite (which had failed) has suddenly materialized. It's still not a mapped drive, but maybe Windows 7 is treating it that way.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments