I have a WinXP Pro machine with mapped drives to our AS400 system, they are
dropping connection during the day. I have tried a few things to change the
time out to drop connection set to 0 so they will stay alive, still not
working. Any other ideas out there that can help.

"keywa" wrote:

> Disconnected Network Drive
>
> To work around the problem (which dogged me for months..) used the standard
> welcome screen WITH MORE THAN ONE USER. One user goes right into Windows and
> mapped drives are disconnected. MORE than one user causes mapped drives to be
> connected when the selected user's settings finishes loading. Bad tradeoff
> to get mapped drives "connected" at startup if only one person uses the
> machine.....
> Wish MS would make a fix to this.... instead of "by design"
>
>
> "_RR" wrote:
>
> > On Tue, 21 Jun 2005 09:48:32 +0200, Thorsten Matzner
> > <tmatzner@gmx.net> wrote:
> >
> > >_RR <_RR@nomail.com> wrote:
> > >
> > >>Any idea what causes mapped network drives to appear as 'Disconnected
> > >>Network Drive' in 'my computer?' This happens even when a system is
> > >>powered up with the networked system already online (supposed to
> > >>reconnect on startup).
> > >
> > >This is by design. Windows will not reconnect the drives on startup
> > >but on the first use.
> >
> > Any way to keep them connected?
> >
> > BTW, drives will reconnect when an attempt is made via direct click in
> > 'my computer' but programs that do folder sync or whatever seem to
> > fail. I wonder why MS would want to force users to manually reconnect
> > after timeouts.
> >
> >

Does anyone have a solution for this problem? I have the same issue on a
WinXP Pro PC that has numerous drives mapped to various directories on
different servers. The PC is in a W2K3 domain and is running all the time.
When we leave for the day, all drives are "connected" and when we come back
in the AM, most of them are displayed as "disconnected network drive".

Any suggestions would be helpful.
Thanks.

"Garling" wrote:

> I have a WinXP Pro machine with mapped drives to our AS400 system, they are
> dropping connection during the day. I have tried a few things to change the
> time out to drop connection set to 0 so they will stay alive, still not
> working. Any other ideas out there that can help.
>
> "keywa" wrote:
>
> > Disconnected Network Drive
> >
> > To work around the problem (which dogged me for months..) used the standard
> > welcome screen WITH MORE THAN ONE USER. One user goes right into Windows and
> > mapped drives are disconnected. MORE than one user causes mapped drives to be
> > connected when the selected user's settings finishes loading. Bad tradeoff
> > to get mapped drives "connected" at startup if only one person uses the
> > machine.....
> > Wish MS would make a fix to this.... instead of "by design"
> >
> >
> > "_RR" wrote:
> >
> > > On Tue, 21 Jun 2005 09:48:32 +0200, Thorsten Matzner
> > > <tmatzner@gmx.net> wrote:
> > >
> > > >_RR <_RR@nomail.com> wrote:
> > > >
> > > >>Any idea what causes mapped network drives to appear as 'Disconnected
> > > >>Network Drive' in 'my computer?' This happens even when a system is
> > > >>powered up with the networked system already online (supposed to
> > > >>reconnect on startup).
> > > >
> > > >This is by design. Windows will not reconnect the drives on startup
> > > >but on the first use.
> > >
> > > Any way to keep them connected?
> > >
> > > BTW, drives will reconnect when an attempt is made via direct click in
> > > 'my computer' but programs that do folder sync or whatever seem to
> > > fail. I wonder why MS would want to force users to manually reconnect
> > > after timeouts.
> > >
> > >