mapped network drive appears to be disconnected in Windows 2003 Server

It prefectly natural that a client PC will drop a connection to a remote network share when not in use.

There are ways to control this behavior in the client PC, but most folks just leave it alone, and just let the PC do what it wants.

Is this behavior causing some kind of problem (other than confusion)

Thanks , but  we run Logistics software that required network drives need to map in Startup otherwise its won’t work ,any other suggestions ?

Do you use Offline Files?
What OS are you using, does it have the latest SP installed?

http://support.microsoft.com/kb/297694 
http://support.microsoft.com/kb/960646
http://support.microsoft.com/kb/938062

Really?  I've seen lots of situations where the network drive "appears" to be offline, but as soon as you try to use it, it connects.   So, it has never caused a problem with any application, script, or user interface.

Are you saying that's not the case... that either A) the drive letter do not magically reconnect when needed?, or B) your software does work unless the drive are fully connected prior to use?

B) your software does work unless the drive are fully connected prior to use?

 yes first drive need to fully connected before our Application load in startup

So, this is like part of a Login Batch file or item in the Startup group?

If so, it might just be an issue of timing...  making the network connection before your app starts  (and might not have anything to do with disconnection)

Fixed myself