>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.

Thanks, I wonder if the issue of non using UNC could be a problem in Windows Server 2003. I assume this is probably fixed in the recent versions. But, if I run into that again, I will change it to UNC. I will then be able to see if that helps once the same pattern will occur again.