New
#1
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. O.o
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