I have several workstations that all have a single, mapped drive F: going to a folder on a server. Occasionally, one or two workstations will just seem to de-activate the mapped drive. It doesn't get disconnected - the drive is still there, but when you go to the drive, it just gives an error saying that it can't find the target. The quick fix for this is easy. If I just browse to the same target server/folder via "My Network Places" instead of the mapped drive, everything instantly comes back to life and the mapped drives work again. Any idea why this would happen and how I can make a more permanent fix?

The obvious has to be loss of connection somehow. You hard drive does have the power scheme to turn off after so long does it? Im not sure if that would effect it. Or maybe a firewall if you have one?

I'm not sure what could be causing the problem. Sounds like another one of those funny XP problems that just seem to happen for no reason. If all the users are logging into a domain, you could create a login script that will map the drive for them each time they log into the domain. EX. net use f: /DELETE net use f: \\servername\drivepath The first statement is deleting th mapped drive and the second is recreating the mapped drive. It is deleted first to make sure the mapped drive is there and available when it is recreated. This would eliminate problems of it not connecting sometimes. hope this helps

If people are logging in, and its not mapping, then the user might not have setup so that the drive maps at connection.

Delete the network drive and then re map them on each machine just ensure your ticking the reconnect at log on box, the logon script is a good way of doing it aswell.

Well, the drives already re-connect when the users log on, and they APPEAR to connect with no problem. But shortly after the desktop loads and they try to access the mapped drive, it just doesn't work. - Jonathan

I had a similar problem, at one point. Actually, it has occured twice for me and it was a different problem each time. The first time it was on the server side. Windows 2000 Server will drop the connection to a mapped drive after a certain period of time. There is a place in the admin tools where you can fix it but I have forgotten where. The command line fix can be found here: http://support.microsoft.com/default.aspx?scid=kb;en-us;297684 I had this problem a second time and it was more persistent. We had just ordered some new Dell's and they came with two CD drives. One of the CD drives had been assigned drive letter E, which is what I liked to assign one of my mapped drives to. I changed the CD drive letter and mapped my drive. It had nothing but problems. I would guess that it was a conflict with some software or registry entry trying to access E as a CD drive but I'm not sure. The quick and easy fix for me, on that, was to just change the drive letter of the mapped drive. It could be something like that, in your case. If you're using lower letters, try making them higher.