A
Abbott
I have a Windows 2000 Professional machine attached in my
Windows NT 4.0 domain. It functions fine on the network,
Internet, and printing except for one thing. At various
times throughout the day I will receive an error accessing
a file or folder on a mapped network drive. There doesn't
seem to be any pattern to when it happens, but it does
happen several times a day. For instance, when you go
into a program under the file menu in an application and
try to pull up a file you've worked on previously, I get
the error. If I try again, it works. Sometimes when I am
in explorer it takes two or three tries to open up a
mapped drive. Then, once I've accessed it successfully,
it seems to work ok for the remainder of the day.
The error is:
An error occurred while reconnecting <drive letter> to
\\server\share
Microsoft Windows Network: The local device name is
already in use.
This connection has not been restored.
I am using login scripts, and have tried disconnecting all
mapped drives and then rebooting/running login script
again; the script runs fine, but then I will get the same
error when I try to access a file on a mapped drive.
Windows NT 4.0 domain. It functions fine on the network,
Internet, and printing except for one thing. At various
times throughout the day I will receive an error accessing
a file or folder on a mapped network drive. There doesn't
seem to be any pattern to when it happens, but it does
happen several times a day. For instance, when you go
into a program under the file menu in an application and
try to pull up a file you've worked on previously, I get
the error. If I try again, it works. Sometimes when I am
in explorer it takes two or three tries to open up a
mapped drive. Then, once I've accessed it successfully,
it seems to work ok for the remainder of the day.
The error is:
An error occurred while reconnecting <drive letter> to
\\server\share
Microsoft Windows Network: The local device name is
already in use.
This connection has not been restored.
I am using login scripts, and have tried disconnecting all
mapped drives and then rebooting/running login script
again; the script runs fine, but then I will get the same
error when I try to access a file on a mapped drive.