Craig
December 12th 03, 07:18 AM
We service several different sites that are running
Windows 2000 server and some Windows XP Professional
workstations. There are several different operating
systems connecting but the problem only shows up on
the XP Pro stations. The drives are mapped through
Network Neighborhood rather than "NEt USE" command in
logon scripts. When the systems have been working or
sitting without accessing the Windows 2000 mapped drives,
if you try to explore through the MY computer to the
mapped drives Windows returns (after some time) the
following
error:
An error occurred while reconnecting drive letter
to \\network server\share folder.
Microsoft Windows Network: The local device name is
already in use.
This connection has not been restored.
This only happens on the XP Pro systems and the Windows
2000 server. On one site they have a Novell server
as well and we can still get to the Novell mapped drives
ever though the Windows mapped drives are not available.
Windows 2000 server and some Windows XP Professional
workstations. There are several different operating
systems connecting but the problem only shows up on
the XP Pro stations. The drives are mapped through
Network Neighborhood rather than "NEt USE" command in
logon scripts. When the systems have been working or
sitting without accessing the Windows 2000 mapped drives,
if you try to explore through the MY computer to the
mapped drives Windows returns (after some time) the
following
error:
An error occurred while reconnecting drive letter
to \\network server\share folder.
Microsoft Windows Network: The local device name is
already in use.
This connection has not been restored.
This only happens on the XP Pro systems and the Windows
2000 server. On one site they have a Novell server
as well and we can still get to the Novell mapped drives
ever though the Windows mapped drives are not available.