mapped srives "fail"

I experience this problem at 2 dififerent sites now. It is as though mapped
drives take long to "activate" after startup. The apps make use of mapped
drives to common data on the server. On restart of a pc and then opening of
the app we get errors relatinf to not finding server data. If we close the
app and go into explorer, then we can view the contents of the mapped drives.
Then we restart the app and it "connects" to the data and runs fine, till we
restart a pc.

The one network is a 2003 Server and pc's in a workgroup, the other site if
XP as a server and pc's in a workgroup

Any suggestions?

Thanks in advance
.

Relevant Pages

  • Re: [PATCH] oom killer (Core)
    ... > because oom killed sshd. ... > who drives 150km to hit sysrq-F or the reset button. ... You'd need a little old computer next to your server with serial console ... and restart the killed app from scratch (to avoid trashing, ...
    (Linux-Kernel)
  • Re: accessing shares when not logged in?
    ... You can use a script to supply credentials when accessing a share or mapping ... > a separate server running Win2K-AS sp4. ... If I run the app ... > when I mapped the drives. ...
    (microsoft.public.windows.server.networking)
  • Re: mapped srives "fail"
    ... drives take long to "activate" after startup. ... the app we get errors relatinf to not finding server data. ... Then we restart the app and it "connects" to the data and runs fine, ...
    (microsoft.public.windowsxp.network_web)
  • Windows 2000 Server and truly permanent network mappings?
    ... I have a crappy little app that is going to run on our server. ... do UNC but I can have that changed in a future release. ... answers I've found are summed up in "The concept of having mapped drives ...
    (microsoft.public.windows.server.general)
  • Re: Mapping drive through service
    ... I have got a server (say in app ... by client it has to map the fileserver to app server. ...
    (microsoft.public.windows.server.scripting)
Loading