Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Drive not mapping, already in use

Posted on 2011-09-20
10
289 Views
Last Modified: 2012-05-12
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.
0
Comment
Question by:jlarger
10 Comments
 
LVL 66

Expert Comment

by:johnb6767
ID: 36569095
reg delete "hkcu\network\f" /f

Or

reg delete "hkcu\network" /f

Then reboot and let the Logon Script remap them.....
0
 
LVL 66

Expert Comment

by:johnb6767
ID: 36569097
Oh, and that's in a CMD prompt....
0
 
LVL 7

Expert Comment

by:mmaris
ID: 36569107
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

 
0
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 

Author Comment

by:jlarger
ID: 36571145
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?
0
 
LVL 22

Accepted Solution

by:
yo_bee earned 84 total points
ID: 36571175
if you goto computer management > disk manager> select HDD and select change drive letter to see if F is even available.  
0
 
LVL 66

Assisted Solution

by:johnb6767
johnb6767 earned 83 total points
ID: 36571182
Odd.....

Wondering if maybe theres a ghost somewhere, maybe under MountedDevices/MountPoints2 in the registry??

Awaiting last question though....
0
 

Author Comment

by:jlarger
ID: 36571256
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?
0
 
LVL 28

Assisted Solution

by:Run5k
Run5k earned 83 total points
ID: 36571631
Jlarger, in the past I have had a few co-workers with similar requests regarding their home networks and they told me that a freeware utility called USB Drive Letter Manager worked well for them:

http://www.uwe-sieber.de/usbdlm_e.html

That being said, I prefer to keep my Windows builds rather lean to optimize both their stability and security, so if I can find a simple alternative to installing another application I normally take that route.  On our domains, we manage to avoid the type of scenario you encountered by ensuring that our log on script doesn't map any network drives within the first half of the alphabet.  Our earliest network drive is "M:" and that always seems to prevent any type of external device conflicts.
0
 
LVL 59

Expert Comment

by:LeeTutor
ID: 37013543
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0

Featured Post

Announcing the Most Valuable Experts of 2016

MVEs are more concerned with the satisfaction of those they help than with the considerable points they can earn. They are the types of people you feel privileged to call colleagues. Join us in honoring this amazing group of Experts.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Article by: Lee
Windows 7 Ultimate and Enterprise (and 2008 R2) introduced a new feature you may not be aware of - Boot from VHD.   Boot from VHD (or what Microsoft refers to asNative Boot allows you to install Windows to a VHD (Virtual Hard Disk) file that is t…
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
This Micro Tutorial will give you a basic overview of Windows DVD Burner through its features and interface. This will be demonstrated using Windows 7 operating system.
The Task Scheduler is a powerful tool that is built into Windows. It allows you to schedule tasks (actions) on a recurring basis, such as hourly, daily, weekly, monthly, at log on, at startup, on idle, etc. This video Micro Tutorial is a brief intro…

837 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question