>I have a server. This one has a map drive to a secondary server. That map drive is set to reconnect at login. So, basically, this map drive should live permanently, even if the server reboots.
>
>However, on one location, if I reboot the secondary server, the main server will reconnect the map drive once the secondary becomes available. But, this will only live for a few hours or days. I then have to go in Explorer, disconnect the drive and reconnect again. This will again run into the same situation. The only way to resolve that issue is to always have the main server to reboot about the secondary server has been rebooted. Following that order, the server will never loose its map drive connection with the secondary server and that can live for months.
>
>Normally, this should not be the case. Even if the secondary server reboots, once rebooted, the server having a map drive to it should see and reconnect to the drive.
>
>Has anyone seen that? Does anyone know a way to avoid that other than the brut force reboot of the server having a map drive to the secondary server?
>
>The server having the map drive and the secondary sever are both Windows Server 2003.

The best solution is to change your apps or processes so they use UNCs instead of mapped drives.

Googling [mapped drive disconnects] gives some useful hits e.g. http://support.microsoft.com/kb/297684

You can use a CMD file to map a drive e.g.

@ECHO OFF

REM Delete the existing mapping, if it exists:
NET USE Z: /DEL

REM Re-establish the mapping:
NET USE Z: \\SomeServer\SomeShare /persistent:y

You can schedule a CMD file like this to run periodically, but you have to be careful to run it in the context of whatever apps or processes need the mapping, as mappings are per profile/session.