Map Network Drive

If you are mapping drives/folders on a NAS, then you will need to use something like User-name@User-PC as your username instead + password.

This was THE most important note in order for my PC running Win 7 Pro x-64 to remember my mapped network drive credentials to a NAS via the Credential Manager control panel. Ish!!!! There were lots of convoluted work-around solutions on the web (there are some really confused people out there!), and your step-by-step with screenshots was by far the simplest and best solution, kudos!!!

For whatever reason if my User name was set to: User-PC\User-name (e.g.), then Persistence was set to: Logon Session. This resulted in having to manually connect to my mapped network drive manually every time I logged back in. But when my User name was set to: User-name@User-PC (e.g.), then Persistence was set to: Enterprise. Which now lets my mapped network drive connect automatically every time I log in.

The key here is to get Persistence: Enterprise.

Oddly enough though, I can use User-PC\User-name with Persistence: Enterprise to access a MacBook Pro laptop.

Just wondering, why couldn't I use Uer-PC\User-name with Persistence: Enterprise for my NAS? My NAS is an Apple Time Capsule which in Win7 reads it like a FAT32 drive. I suppose the MacBook Pro and the Time Capsule have slightly different file sharing protols.

What is the best way to take control of the Persistence setting in Credentail Manger?

Thanks Brink!

I have almost the same problem. I have a NAS usb drive connected to a server. The server itself has restrictions where only certain accounts (admin accounts) can access the server. This one user has both a regular and an admin account. He first logs onto his own desktop using his regular account. He can map to the c:\drive on the server by checking "Connect using different credentials" then mapping. But he cannot use this same process to map to the NAS usb drive(z:\). If he logs into the desktop with his admin account, he can map both the c and z off of the server. But here's the catch-he can log in on another desktop using his regular account, that's on the same domain, and go through the process of mapping the drives from the server for both the c and z drive using the "Connect using different credentials" with no problems. FYI-when this user tries to map the z drive from the first computer by "Connect using different credentials" and the screen comes up to enter the other credentials. After entering his "admin" credentials, nothing happens-no errors or warnings. The screen just stays there with his admin account name and the password line is blank. Another FYI-I can map the NAS z"\ drive by following the same procedures and the first user. It looks like a profile problem but what?

greetings - I followed to this tutorial from tenforums how to remove map network drive in windows 10 - Windows 10 Forums where inimitable Brink directed an "unmap" query to this tutorial, specifying Option 2. I am running win10 build 14393.693

When I follow the instructions, Option 2, Method 1 the system responds that the drive is not found. I had previously attempted the 'easy way', but what that did was leave the mapped network drive alive and well, but with the red-X associated, marked "disconnected", as though we were sleeping and had just awakened [which is the original issue I've been trying to remedy]. I can browse that 'disconnected' drive just fine. If I right click and pull the context menu, it shows the "disconnect" command; no "connect" command.

since I know the mapping routine [but obviously not the UNmapping routine], I would like to be rid of the network drive mapping, then recreate it. How do I do that for real?

thx z

thank you sir!
as it turned out [embarrassingly] I needed a full restart. after that, gone.