Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Disconnected Mapped Network Drives - Red X's

Status
Not open for further replies.

CoreyWilson

IS-IT--Management
Feb 3, 2004
185
CA
Hello all,

My Citrix clients were/are having an idle timeout issue with there mapped network drives, where they receive an x after a prolong period of inactivity. I had not changed this from the default until three days ago. On each of the servers I set the command net config server /autodiscconect:-1 and it says command succesfully applied. However some users still end up receiving these red x's EVEN if they were users logged off before applying the changes. I also set this one the server hosting each of the mapped network drives. All my citrix users use roaming profiles, and Im wondering if somewhere in there roaming profile it is saving this old setting and not updating it with the change I made to the servers to disable the timeout value on mapped drives. The biggest problem here is users personal address books as well there personal folders are stored on there network drives, so needless to say when and if they open outlook before opening a drive in the morning that is x'ed out they receive errors stating outlook cannot find the specified files and what have you.

Is there a trick to resolving this issue? Also, I restarted all three servers last night and reset this command as soon as they came up to ensure it was loading clean and no user sessions were active.

Thanks!
 
I ahve seen this in the past when the server you are connecting to visa mapped drived does not have sufficiect licenses installed through Settings/Control Panel/ Licenses. We had 20 users mapping a drive to a file server, but there were only 10 installed (our default). Once I added the CAL's that the client actually purchased, the issue went away. Not sure if when a new connection is made, it drops the connection that has nnot been accessed for the greatest amount of time, but this is how we resolved it...

Mike Brown CCA
 
Here is what worked for me:

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" (without the quotation marks).

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.

NOTE: This step must not be confused with the remote access Autodisconnect
parameter that is turned off if you set it to a value of zero (0).

If you set Autodisconnect to zero (0), this setting is not turned off and
after a few seconds of idle time very fast disconnections can occur.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top