Mapped drives don't come back.

[Guest]

First let me say this before I hear the same old message that we shouldn't
use mapped drive letters anymore. Unfortunately, this customer has an App
that requires it. Here is the problem:

Currently experiencing an issue where our two mapped network drives will
show up as disconnected network drives when the system is logged back in at
the start of the day. We have checked all updates and SP levels...all are
OK. Nothing out of the ordinary in the Group Policies, and power management
settings have been disabled. We run quite a few large networks and only see
this problem on our Windows 2003 domains. Problem only seems to occur if the
login script runs when the client is logging back in after the system has sat
while logged out overnight. Once the problem happens, the only remedee so
far has been to reboot.....net use doesn't show the drives at all, however
you cannot re-map as it generates an error about the device being in use. If
you double-click the drive in My Computer it will open just fine....but the
drive still says that it's a disconnected network drive. Suspected the login
sript when I started noticing that when manually running it after a fresh
reboot the drives would immediately show up as disconnected. I modified our
login script to not remove the two network drives but to still remove any
other network drives before trying to remap them......seemed to work good in
testing.....ran the new script more than 5 times in a row with no problem,
and immediately saw the problem when running the old script on the 6th test.
Put the new script in place and checked the next morning when the user logged
in.....same issue.

Anybody have an idea of something else to try?

 

[Pegasus \(MVP\)]

First let me say this before I hear the same old message that we shouldn't
use mapped drive letters anymore. Unfortunately, this customer has an App
that requires it. Here is the problem:

Currently experiencing an issue where our two mapped network drives will
show up as disconnected network drives when the system is logged back in at
the start of the day. We have checked all updates and SP levels...all are
OK. Nothing out of the ordinary in the Group Policies, and power management
settings have been disabled. We run quite a few large networks and only see
this problem on our Windows 2003 domains. Problem only seems to occur if the
login script runs when the client is logging back in after the system has sat
while logged out overnight. Once the problem happens, the only remedee so
far has been to reboot.....net use doesn't show the drives at all, however
you cannot re-map as it generates an error about the device being in use. If
you double-click the drive in My Computer it will open just fine....but the
drive still says that it's a disconnected network drive. Suspected the login
sript when I started noticing that when manually running it after a fresh
reboot the drives would immediately show up as disconnected. I modified our
login script to not remove the two network drives but to still remove any
other network drives before trying to remap them......seemed to work good in
testing.....ran the new script more than 5 times in a row with no problem,
and immediately saw the problem when running the old script on the 6th test.
Put the new script in place and checked the next morning when the user logged
in.....same issue.

Anybody have an idea of something else to try?

Try this from a Command Prompt:
net use * /del
net use /persistent:no

Now make sure to do this:
- Map all your network drives with explicit "net use" commands in your
logon script instead of relying on remembered connections.
- Do not map any network drives in tasks run by the Task Scheduler.

 

[Jody White]

First let me say this before I hear the same old message that we shouldn't
use mapped drive letters anymore. Unfortunately, this customer has an App
that requires it. Here is the problem:

Why aren't you suppose to use mapped drive letters anymore? What are
you suppose to use?

 

[Richard G. Harper]

The preferred method is using a UNC (Universal Naming Convention) path, such
as:

\\server_name\share_name

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm