mapped drive silently disconnects while working

[suewilson]

have several xp pro machines, all with the same issue. a
mapped drive works fine until the connection to that
drive has been idle, when the user attempts to access a
folder on the mapped drive, they get an unavailable error
for the drive letter. it's almost as if the network
connection hibernates. terrible, terrible enhancement
to the networking environment. how to i force these
machines to keep the connection live.

 

[bob lin]

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.