Drive mappings get disconnected randomly when mapping with a login script

We run a .bat file at login on our Windows domain.  We have a Windows 2003 Server domain controller, and Exchange 2003 server, and a Windows 2003 Member Server on our network.  The batch file simply maps netword drives to our client PC's.  I find that pretty much everyday, these dive mappings seem to go away.  They don't go away in the sense that they dissappear, but rather just say "disconnected".  I simply double click on then, and it will reconnect (individually).  We have a couple Windows 2000 Pro machines, and their network drives get a red X on them and sometimes double clicking on them don't bring them back to life.  I can't seem to figure out the frequency or timing on when they get disconnected.  Any ideas?
Who is Participating?
Brian PierceConnect With a Mentor PhotographerCommented:
tigermattConnect With a Mentor Commented:
I believe the drives timeout after a certain period of inactivity - i.e. if you don't access files for a length of time the server disconnects the connection.

There's nothing to worry about, this is normal behaviour.
LauraEHunterMVPConnect With a Mentor Commented:
You can also configure the Server service on the file servers in question to never auto-disconnect.  On each server in question, run the following command:

net config server /autodisconnect:-1
jbobstAuthor Commented:
Thanks for the input.  That seems to be the problem/cause!

I'll splt the points if you don't mind.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.