Windows 10: mapping/mapped drives

I have a Windows 10 Pro fully updated computer that has three folders on a second drive not the boot drive. I created three usernames/passwords on this computer and gave rights to each user for each folder. When I go to any one of the computers 8-10 on the network workgroup I can map a drive using different credentials for each folder. But I can only map one drive the others will say "The network folder specified is currently mapped using a different user name and password.", but it's not or maybe it is and I'm missing something. There were mappings to a NAS device that had the data but it died so I put the backup on one computer and shared it out. Let's say the folders names are "Sales", "Accounting" and "Office". I can map Sales on one computer but can't on another using the same credentials. Same with the other folders, can map one folder on one computer but not another. What am I missing? Most or all have the 1909 update and some the 2004 and all are Windows 10 Pro.


Some more info, on the root of D: drive I have two folders, one is Accounting the other is Office, the Sales folder is a subfolder of Office. The "acct" user I made has access to the Accounting folder and so on with the others. Do I need to create users on the sharing computer with the same name and password as whoever logs into one of the network computers? I hope not. I have tried running mountvol /r from an elevated command prompt but that has little to no effect.


Thanks for any help on this,


Dan

:)

 

Work Mapped drives not working at home.


Hello All.

I have a user at work that has a laptop as her main work use (docking station at work, then takes it home to work at home).
we have a list of mapped network drives that we use here, including a personal drive.

however when this user gets home or off the network, the personal drive seems to become inactive/go missing.

there are no USB drives that interfere with the network drives, and i am lost looking for solutions.

any suggestions/help would be greatly appreciated.

thanks.

 

Map Network Drive in Windows 10


Hello cognus,

I find the best way to keep a mapped drive always available is to use OPTION ONE and select Reconnect at sign-in at step 5.

The (Remains connected after next logon) command in the other options should work for you as well though.

It's normal for the mapped drive to have a red X on it after not being used for a while, but clicking on the drive should have it be automatically connected again after a short wait sorta like waiting for a HDD to spin back up after being turned off when idle.

I'm not aware of a way to keep a mapped drive to always stay active.

 

Mapped drives not showing up on Explorer

Wanted to mention that I'm experiencing this same issue. Environment here is a Windows Server 2012 R2 domain with network shares and printers mapped by GPO. GPO drive mappings are not on a per-user basis and instead are global for all users.

Affected user can not access mapped drives via explorer, yet NET USE shows drives mapped as expected. Attempting to remap network drives via explorer results in a prompt stating that the connection is already mapped to that drive letter, do I want to disconnect and reconnect it?

Oddly, using applications that provide an 'open document' dialogue can see and access mapped network drives normally. For example, open Word, file -> open -> browse: Left pane shows network shares, clicking on network share shows share contents. Clicking on 'This PC' shows all mapped drives which are navigable and documents can be opened normally. Doing this does not correct the issue with Explorer. Similarly, a command prompt also operates as expected, so it's possible to change to a mapped network drive by the associated letter and to list / copy / delete files normally.

Issue appears to be limited to a single user profile on the workstation displaying the described symptoms. Logging in as another user results in the drives being mapped and accessible as usual. Symptoms persist through reboot. User account with symptoms does not have admin access locally or on the domain.