Re: Lost drive mappings

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Robert L [MS-MVP] (noreply_at_hotmail.com)
Date: 08/12/04


Date: Thu, 12 Aug 2004 10:14:41 -0500

quoted from http://www.ChicagoTech.net
Some network drives show with a red 'X'

Symptoms: you have mapped some network drives and checked the reconnect at
logon, or your network uses logon script to map network drives. After
rebooting, some network mapped drives may show with a red 'X'. If you click
on the drive, it becomes active.

Cause: net use /persistent:yes is default settings for NT and win2000/XP.
This is why when you have mapped some network drives and check the reconnect
at logon, or your network uses logon script to map network drives, the
mapped network drives may show red Xs after rebooting. If you enable echo
and pause the logon script or if using net use to map the same drive
manually, you may get "System error 85 has occurred. The local device name
is already in use." One thing you may want to try to avoid the red X is
using net use /persistent:no, for example, net use i: \\servername\folder
/persistent:no.

-- 
For more and other information, go to  http://www.ChicagoTech.net
Don't send e-mail or reply to me except you need consulting services. 
Posting on MS newsgroup will benefit all readers and you may get more help.
Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on 
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
"Richard" <rsuggitt@fdrinnovation.com> wrote in message 
news:487701c4804d$10c91ff0$a301280a@phx.gbl...
>I run XP Home on my PC and access a Windows NT server via
> a small Lan.  I have defined mappings to 3 shared drives
> in the server to drive letters F, G, and H.  All are
> defined with the 'reconnect at logon' option ticked.
> All worked fine until I changed the LAN card in my PC to
> a 3Com 1Gb card (model 3C2000); whenever I boot the PC
> now, these mapped drives are unavailable.  If I go into
> Windows Explorer I can see the drives under 'my
> computer'; the drive letters have an X through them.  If
> I open 'My Computer' from the Start menu I again can see
> the drive letters but they again have an X through them.
> If I then double-click on each drive letter in turn, they
> open and I can see the contents of each drive, and the X
> disappears, and I can use data and apps on these drives
> OK (until the next reboot).   As far as I can see I am
> logging into the server domain/workgroup OK, there are
> successful login entries in the event viewer.  Other XP
> PCs on the same Lan (including those which have had
> similar Lan card changes) do not have these problems and
> connect to the server drives OK when they boot.  Any
> ideas what's causing this failure to map the drives ? 


Relevant Pages

  • Re: Logon mapping
    ... > After fixing my slow connection to Server 2003 with an XP ... > machine I have now mapped the drives and all is great. ... > When I mapped them I did select to reconnect after logon. ...
    (microsoft.public.windows.server.general)
  • Re: Mapping Drives
    ... >> machine I have now mapped the drives and all is great. ... >> When I mapped them I did select to reconnect after ... >> and changed the user to my logon to the server. ...
    (microsoft.public.windows.server.networking)
  • Re: Automatically Reconnecting Mapped Drives
    ... map a network drive and have the drive reconnect at logon. ... I'm not even prompted upon Windows ... mapped drives at logon? ...
    (microsoft.public.windowsxp.general)
  • Re: Mapped drives dont connect....
    ... wait for the network at computer startup and logon" to ... >> drives to a 2000 server. ... The user account won't reconnect the drives ... >Microsoft MVP Scripting and WMI, ...
    (microsoft.public.windowsxp.security_admin)
  • Logon mapping
    ... After fixing my slow connection to Server 2003 with an XP ... machine I have now mapped the drives and all is great. ... When I mapped them I did select to reconnect after logon. ...
    (microsoft.public.windows.server.general)