Windows 10: Can't map drive, says the resource is already in use with this user

I have a Linux File-server that I have had the M: drive mapped to for almost 2 years. I recently rebuilt my windows 10 pro build 3 weeks ago, and one of my first steps was remapping the drive, and that worked as it has before.

But just this Saturday, a program was trying to save a file there and it said the drive was invalid. This is typical when I reboot and I have yet to try and open he drive and supply my credentials (they were not saved even though I always check save credentials)

Once I supply the password, and the file explorer pops open in the root of the share, the program that needed the drive suddenly is happy and things go forward.

This time that did not happen. So I disconnected the drive, and tried to remap it. When I was prompted for my credentials and supplied them, I was told that it was unable to map this drive using the credentials provided because this resource was already in use with those credentials.

I don't have any other mapped drives to that server, or to another server in my home domain that would use my home domain credentials. So I thought I fresh reboot would help clear up the issue.. It did not.

How might I tell how windows thinks I am already using this resource so I can clear it and just start a new?

The SAMBA share is \\mondo\data (Ubuntu 18 LTS Server) using the SAMBA NTLM domain\user nickellson.com\grimm and this share would be the only thing I would use on this server, and would have to be using that username.

Nick

:)

 

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


thank you for doing this tutorial.
An issue that plagued us in earlier Windows still remains in 10 and I do not yet understand some of the solutions given in the superuser forum thread pasted below.
The issue is simple:
- "drives" are mapped correctly, and work well WHEN they are manually accessed.
- Windows 10 automatically disconnects the resource when not used.
- Waking or restarting/booting the mapped drive remains disconnected: no request has been made, therefore the shared resource is offline [Red X]

the solution would be something to cause the mapping to be ready/available/connected at all times except for sleep [I guess... that would be permissible to most] or 'off'. In the thread below a couple of people propose 'solutions' [despite a couple of boneheaded ideas] but these either over-reach or are limited only to solving the 'connect at startup' need.

Not solving this defeats automated routine backups [pushed from the client station in question, in this example], which can be deadly. users should not be expected to have great memories or great technical skills

what is the RIGHT step to take to make the Mapped resource "always available", with exceptions noted above?

On login, how do I get Windows to mount/connect a mapped network drive automatically? - Super User

 

The mapped name of a folder is stuck


I have never had to do anything else to remove an old network drive mapping. [The mapped drives I have are all listed even though they are not currently connected].

If I understand the situation correctly -

• You have mapped \\TOWER\0 SYNCHRONIZ and that is confirmed by HKEY_CURRENT_USER\Network
• But File explorer insists that you have mapped to a [removable?] drive you have called 0 SYN that is connected to the network computer called T instead

1 Does HKEY_CURRENT_USER\Network contain an entry for 0 SYN or \\T at all?
2 Does HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Portable Devices\Devices contain 0 SYN as a 'FriendlyName' entry?
3 Can 0 SYN be found in your Registry elsewhere [such as HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares]?

Denis