Todd, This had me puzzled too but the network connection always
reconnects without any problem. It doesn't seem to have any adverse
affect on running Vantage (or any other program) so I just left it
alone. It's not so scary once you read this article.
Here is the answer: (MS Knowledge Base Q297684)
Drive Mapping May Time Out on a Windows 2000-Based Computer
The information in this article applies to:
Microsoft Windows 2000 Professional
Microsoft Windows 2000 Server
SYMPTOMS
When you perform drive mapping from a Windows 2000-based client
computer to either a Microsoft Windows NT or Windows 2000 network
share, the drive mapping may be disconnected after 15 minutes of
inactivity and Windows Explorer may display a red "X" on the icon of
the mapped drive. However, if you attempt to access or browse the
mapped drive, it reconnects quickly.
CAUSE
This behavior can occur because both Windows NT Server version 4.0
and Windows 2000 Server can drop idle connections after a specified
time-out period, which by default is 15 minutes, so that server
resources are not wasted on unused sessions. The connection can be re-
established very quickly at a later time, if required.
RESOLUTION
To resolve this behavior, use a command to change the default time-
out period on the Windows NT Server 4.0 or Windows 2000 Server: At a
command prompt, type: net config server /autodisconnect:30.
The valid value range to configure this setting from a command line
is from -1 through 65,535 minutes. To disable Autodisconnect, set it
to -1.
--- Original Message ---
Message: 5
Date: Tue, 2 Oct 2001 16:57:02 -0500
From: Todd Anderson <tanderson@...>
Subject: [Off Topic] Windows-2000-Pro connectivity issue
I'm trying to debug a Windows-2000-Pro connectivity issue and am
looking for some help.
Here's what's happening:
* Dell Optiplex GX150 - running Windows-2000-Pro
* Using my logon which is Network-Administrator
* Using logon scripts that connect my machine to about 15 network
drives
* From within "Explorer" I can see all of my network drives ...
However, some of the connections are showing a RED X under the drive
icon on the left side of the screen. I can still browse them and
copy to them. The RED-X's float - ie - at times I will only see one
connection with a RED-X while at other times I'll see 5 or 6. Their
appears to be no direct correlation to specific servers.
* Also, when a connection shows a RED-X and I'm using software to
try and access files or applications via these connections I will
sometimes get a pop-up box with the following error:
*** An error occurred while reconnecting S: to \\server\share
*** Microsoft Windows Network: The local device name is already in
use.
*** The connection has not been restored.
I'm trying to decide if this is a hardware issue with the integrated
3COM-905C NIC or if it is related to Win-2000-Pro.
We currently have 4 machines with this configuration all of which
rarely use Vantage. I would like to isolate this behavior before
installing Win-2000-Pro on machines that will be using Vantage since
I strongly suspect that what ever is disconnecting these connections
will probably give Vantage the fits.
Any ideas would be greatly appreciated.
Thanks,
Todd Anderson
reconnects without any problem. It doesn't seem to have any adverse
affect on running Vantage (or any other program) so I just left it
alone. It's not so scary once you read this article.
Here is the answer: (MS Knowledge Base Q297684)
Drive Mapping May Time Out on a Windows 2000-Based Computer
The information in this article applies to:
Microsoft Windows 2000 Professional
Microsoft Windows 2000 Server
SYMPTOMS
When you perform drive mapping from a Windows 2000-based client
computer to either a Microsoft Windows NT or Windows 2000 network
share, the drive mapping may be disconnected after 15 minutes of
inactivity and Windows Explorer may display a red "X" on the icon of
the mapped drive. However, if you attempt to access or browse the
mapped drive, it reconnects quickly.
CAUSE
This behavior can occur because both Windows NT Server version 4.0
and Windows 2000 Server can drop idle connections after a specified
time-out period, which by default is 15 minutes, so that server
resources are not wasted on unused sessions. The connection can be re-
established very quickly at a later time, if required.
RESOLUTION
To resolve this behavior, use a command to change the default time-
out period on the Windows NT Server 4.0 or Windows 2000 Server: At a
command prompt, type: net config server /autodisconnect:30.
The valid value range to configure this setting from a command line
is from -1 through 65,535 minutes. To disable Autodisconnect, set it
to -1.
--- Original Message ---
Message: 5
Date: Tue, 2 Oct 2001 16:57:02 -0500
From: Todd Anderson <tanderson@...>
Subject: [Off Topic] Windows-2000-Pro connectivity issue
I'm trying to debug a Windows-2000-Pro connectivity issue and am
looking for some help.
Here's what's happening:
* Dell Optiplex GX150 - running Windows-2000-Pro
* Using my logon which is Network-Administrator
* Using logon scripts that connect my machine to about 15 network
drives
* From within "Explorer" I can see all of my network drives ...
However, some of the connections are showing a RED X under the drive
icon on the left side of the screen. I can still browse them and
copy to them. The RED-X's float - ie - at times I will only see one
connection with a RED-X while at other times I'll see 5 or 6. Their
appears to be no direct correlation to specific servers.
* Also, when a connection shows a RED-X and I'm using software to
try and access files or applications via these connections I will
sometimes get a pop-up box with the following error:
*** An error occurred while reconnecting S: to \\server\share
*** Microsoft Windows Network: The local device name is already in
use.
*** The connection has not been restored.
I'm trying to decide if this is a hardware issue with the integrated
3COM-905C NIC or if it is related to Win-2000-Pro.
We currently have 4 machines with this configuration all of which
rarely use Vantage. I would like to isolate this behavior before
installing Win-2000-Pro on machines that will be using Vantage since
I strongly suspect that what ever is disconnecting these connections
will probably give Vantage the fits.
Any ideas would be greatly appreciated.
Thanks,
Todd Anderson