jlarger
asked on
Drive not mapping, already in use
I have a login script to map network drives for users. One user, who happens to be at a remote site with a site-site vpn, is having issues with the script. One of the drives is not mapping successfully. The other drives map correctly without issue. If I try to manually map the drive with command prompt Net Use command, I get System Error 85, already in use. There are no drives physical or otherwise that I can see using the letter F. If I try to navigate to the path and right click and map, F is not presented in the drop down. It is really important that this mapped connection use the letter F
I tried command Net Use * /delete, which deleted all of the connections but did not specifically state F. Still unable to map to that letter manually.
I tried command Net Use * /delete, which deleted all of the connections but did not specifically state F. Still unable to map to that letter manually.
Oh, and that's in a CMD prompt....
Either the local drive letter is used by a USB mass storage device or else it is remembered from a previous session. Run the following commands just once to fix the problem:
net use * /del /yes
net use /persistent:no
Also try:
http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/system-error-85-has-occurred-the-local-device-name/d8bfc6c1-2476-4055-920d-89813fd6494d
net use * /del /yes
net use /persistent:no
Also try:
http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/system-error-85-has-occurred-the-local-device-name/d8bfc6c1-2476-4055-920d-89813fd6494d
ASKER
johnb6767: 1st command returned with error that file did not exist. 2nd command complete succesfully. On reboot, did not successfully map the drive. Manually tried to map with same System Error 85.
mmaris: I agree something is holding F as a reservation for whatever reason. Ran both commands successfully. Did not fix issue. Link more or less rehashes what we have tried here, so no go there.
Other suggestions?
mmaris: I agree something is holding F as a reservation for whatever reason. Ran both commands successfully. Did not fix issue. Link more or less rehashes what we have tried here, so no go there.
Other suggestions?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Now I just feel silly. Could have sworn I had already checked this, actually I'm sure I did I just must have missed it. In opening Computer Management > Disk Manager I found F was assigned to an empty removable device (facepalm). Reassigned that drive letter and now all is well.
Is there any way to prevent Windows from assigning the F letter to devices in the future?
Is there any way to prevent Windows from assigning the F letter to devices in the future?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
Or
reg delete "hkcu\network" /f
Then reboot and let the Logon Script remap them.....