Windows 10: Unable to map network drive (apparently already mapped)

So I want to map a network drive on windows 10 and were able to in the past, but now when I try to log in my server I get the 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.


(The directions and log in credentials were correct I checked it on another pc)



Oke, so I checked in CMD if there where any mapped drive using:

net use > mapped_drives.txt

But I Could't find any mapped drives.


How can I fix this?
How can I log in my server again?

:)

 

Unable to disconnect from mapped network drive

I receive the following error when I try to disconnect from a self mapped network drive: "network connection does not exist"

The network drive icon appears with a bid red x and says it is disconnected, yet I can double click on it to enter the mapped folder. Doing this does not reconnect the folder, and remains disconnected. This causes problems because programs that pointed
to this path are unable to read the files. I am unable to remap this drive because the associated drive letter (E and mapping no longer shows up in the list.

I've tried all the typical suggestions including:

--I tried to do it via the command prompt with the net use delete command, but it can't be found in there.

--Tried to above with the actual network path instead of the drive letter, did not work

--Tried to delete the registry entries from:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2

HKEY_USERS\. Default\Software\Microsoft\Windows\CurrentVersion\Explorer\Mountpoint2\

None of these solutions worked. Though deleting the registry entries momentarily hid the disconnected drive, the drive letter was still not available for mapping. I tried to force the drive letter (E to map to my optical drive, which worryingly, pointed
back to the mapped network location on the NAS instead of to the optical drive.

How do I get rid of this? Reformatting the computer is not an option.

 

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.

 

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.