XP and mapped drive problem...

I have a user who is running XP SP1. I'll check on updates he may need shortly. In the mean time I was wonder if you guys could give me some suggestions. We're on a Windows 2000 AD domain/network. I have a user that is running XP. When the user logs in a script runs that maps some drives to network resources. All the drives are mapped and good to go for a week or two and than suddenly one of the drives disconnects. There is no indication that it has disconnected. He tries to go to the mapped drive and finds that it is missing. It is the same mapped drive every time. This user turns off his PC almost daily so it doesn't appear to be something like the PC was on too long and needed rebooting. I searched MS KB and found nothing. Any ideas?

So, the script runs everyday because he logs on every day. Correct?

On the days that the mapped drive is not available, are you sure it connected in the first place?

If the machine is left on, does rebooting help?

Tropical, no we're not sure it connected in the first place on days when the mapped drive is not available. He only notices it is missing when he tries to go to it using something like Word or Excel. It is possible that it didn't connect at all for some reason. I didn't think of that.

Steve, rebooting seems to have helped every time this has happened. When he notices it is missing he reboots, logs on and the G: drive shows up.

His other drives apparently are always there, unless he never uses them so he does not notice they aren't there, either. His login script is used by 100 other people, too, and I've heard no other complaints from them.

I have 4 pc's at my desk in the office. Have mapped drives going back and forth etc... (xp,xp,win2k,win2kserver)


I can open explorer at any given time and see the mapped drives with red x's. Clicking on em re-connects them...

I've disconnected the drive that is mapped via login script (.bat file) and have mapped it manually from the command prompt using the persistent switch. Now we have to wait and see if the problem happens again...

Hi

did you ever fix this problem? I have a similar issue.

I'm thinking that I ended up setting up a persistent static mapping to that network drive. The user never logs into another PC, and if he were to do that his regular login script would run and map the drive for him. But on his PC I think I did a static persistent mapping. Another option for you to look at is here - http://support.microsoft.com/?kbid=138365