I have a scenario. I have a laptop joined to and signed directly into a Domain. There are five mapped drives. Each drive is accessible and re-maps upon reboot. When the machine is taken home it again logs into the Domain using cached credentials, The five drives still show as mapped but I guess nothing is really there. We make a software VPN to our Router. When an attempt to browse those mapped drives is made we get: An error occurred while reconnecting S:\\101..... The local device name is already in use. If we try to start\run \\101..... we get: 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 and try again. If I go to any machine not on the domain with no cached credentials or mapped drives and make the vpn connection it connects fine and I can browse the shares and provide credentials and I am in. What do I need to do? I really don't want to disconnect the shares as I would like them to appear when the machine is not on the vpn. Is it the cached credentials? We did try signing in as one of the local machine users and it works as it does not map the drives. But that is not a viable option as we need the mail client profile and of course the desktop, etc. Any ideas?

Hi, Thanks for the post. This issue may occur if you log on to the Windows client by using a different connection type than you use to connect to the file server. If you created the network drive through a local area network (LAN) with your current user credentials, the mapping information does not contain any user information. When you log on to the computer, the operating system establishes only a partial connection to the share, and the network drive is considered used. Later, when you access the network drive, the connection is fully restored. If you use another connection type such as Remote Access Service (RAS) to connect to the file server, the logon credentials used are different from the credentials that you used to create the network mapping. When you try to access the network drive to restore the connection, the operating system tries to use the logon credentials of the RAS connection. If the file share server does not accept the logon credentials of the RAS connection, the operating system cannot access the share. Then, the operation system tries to re-create the mapping to the already-used network drive, and the error occurs. To resolve this issue, remove the existing network mapping. Then create a new network mapping for the share. Thanks, Miles Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Miles When we are at corporate where we made the mappings we use a LAN port and a wired cable. When the attempt to work remote is made we are using a wireless connection to reach router/Internet. When we log on we use the same Windows Logon/password/domain. Cached credentials are passed. The remote connection is not RAS or any dialup but a software vpn client that only passes vpn credential in order to bring up the vpn tunnel. Does that change anything about your answer? I ask because I am told that the mapped drives were disconnected/removed at corporate and the laptop was brought remote, signed on to the Domain with cached credentials, vpn was made and then the server was browsed for at \\101.6.xx.xx\share and still failed. The cached credentials seem to be the wildcard as I can connect no problem but I am from a workstation not formerly joined to any domain so I have no cached credentials.............I am confirming what the exact "still failed" message was/is.