Mapped network drive letter not available in command prompt
Hello,first post here!The following is happening:While mapping a external share to a drive letter, the drive letter is not availableon the command line.Running as administrator does not resolve this.Is this a permissions issue? On my test machine it works fine, but on a client'smachine I can't get them to show up no matter what I do. Only physical drivesare available on the cl, but all mapped drives are available when using the UI.Hope you can help.Marinus.
October 19th, 2007 5:48am

I got exacle the same. And a Windows program (ActiveSky) won't run properly because of this:it can not find shared folders on a different computer. Drive free space info in 'My Computer' is also not shown for the mapped drives until drive is opend via explorer. So looks like a network connection not opening. I tried: Different (new) user on same machine. And various batch files dir f:\ and looked at NET ... commands. Changing network tcpip and sharing options This all fails. It seems I just found a workaround (need reboot to test properly) Opening the maped drive via the explorer command line options, putting this in STARTUP using a shortcut (explorer /n,f:\ to open the f: drive) However this leaves open unwanted windows. So looking at a proper solution on how to access mapped network drives from command prompt, that is how to open the network connection properly so windows programs and cmd promt do find and open mapped drives. Hajo
Free Windows Admin Tool Kit Click here and download it now
October 22nd, 2007 9:17am

Unfortunately this warkaround also did not work on statup: An error occured while reconnection F: to [\\pc\share]the requested recource is in use connection has not be restored. So how to get network connections really active on system startup automatically (so without first browsing via My Computer)? BTW:this occurs on aWorkgroup solution, just connecting 2 PC's, connected via tcp/ipusing fixed IP addresses. Marinus: what network setup do you have problems with? Hajo
October 22nd, 2007 9:44am

Hoi Hajo,the setup is Vista to a Buffalo TeraStation (Linux/Samba) on a LAN.I fixed it with SUBST but that's pretty ugly; I have to do SUBST S: T: and SUBST S: /e when I'm done syncing.S: is the letter of the mapped drive, which is available through Explorer.A normal solution would be nice. If you find out anything more then let us know.Marinus.
Free Windows Admin Tool Kit Click here and download it now
October 26th, 2007 12:10am

I've just come across this on my vista machine and NAS. I used "cmd S:" from the start --> run menuand whilst the command window opened on the c drive,it then recognised the s: drive. TJeffer
January 18th, 2008 7:40pm

Hello. This is an old topic, I know, but it carried over to Windows 7 and this article came the closest to the issue I was searching for. Through "trial and error" I found a solution to the problem I was seeing like this by: 1) make sure the command prompt was opened as an administrator (allows access to all folders) 2) use the command "net use <drive letter> \\<servername>\<sharename>" for the share you need to access I recommend trying this without running the prompt as an admin first to see if it does what you need. In my case, I was copying shortcuts to the c:\users\public\desktop folder through a batch file to install custom utilites we use, so I required the admin access. Also...and this may be a Windows 7 thing as didn't use Vista much...I found that in a standard (non-admin) command prompt session, I could access the network shares, but I could not through an admin command prompt. I found that I could include this line as part of the batch files I use as long as the batch files were run as an administrator. It worked like a champ. -Scott
Free Windows Admin Tool Kit Click here and download it now
April 21st, 2010 3:53pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics