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
Windows & Network Support, Tips and FAQs on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
"Gary Davidson" <(E-Mail Removed)> wrote in message
news:0bcf01c3770c$71c9a860$(E-Mail Removed)...
> Windows XP Pro and XP Home PC's have a problem
> automatically logging on to mapped network drives on a
> variety of servers (XP peer-to-peer - Win 98 server - Win
> 2003 Server).
>
> The mapped drives are set to logon automatically and they
> always setup just fine but when the PC is rebooted, the
> drives have the red X on them. If the drive icon is
> double clicked, the drives are then available and stay
> available as long as the PC is not rebooted.
>
> It isn't a timeout thing because they have the red X
> immediately upon boot up and they stay on after they are
> double clicked.
>
> Thank you
Similar Threads
