Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows NT / Setup / December 2004

Tip: Looking for answers? Try searching our database.

Windows 2000 PC's drive mapping disconnecting from NT 4 Server

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Rob Nicholson - 20 Dec 2004 11:17 GMT
Our Windows 2000 PCs keeping disconnecting their drive mapping to one of our
NT 4 servers - the only used to host the user's home drive. This is darn
annoying as you loose your favourites, "my documents" etc. If you open My
Computer there is a red X by the O: drive. Hitting refresh a few times and
the X disappears and the mapping reconnects.

However, the S: and T: drive mappings, to a different NT 4 server, never
exhibit this behaviour.

KB article 297684 mentions setting the autodisconnect value in the following
key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters

We've set it to -1 but it's still disconnecting. Do we need to reboot the
server for it to take effect?

Interesting, the other server which doesn't exhibit this problem has
autodisconnect set to 0xf (15 mins). We are often idle for >15 mins but
these drive mappings never disconnect. Which kind of suggests it might not
be autodisconnect from the server that's causing the disconnects. Is there
anything client side?

Thanks, Rob.
Kaushik Banerjee - 21 Dec 2004 00:00 GMT
Hello,

To ensure that the autodisconnect feature is turned off I want you verify
the steps:

NOTE: If you use this method, you may turn off the autotuning feature for
the Server service.

To change the default time-out period for the autodisconnect feature of the
Server service, open a command prompt, type the following line, and then
press ENTER
net config server /autodisconnect:number
where number is the number of minutes that you want the server to wait
before it disconnects a mapped network drive. The maximum value for this
command is 65,535.

NOTE: If you set the autodisconnect value to 0 (zero), the autodisconnect
feature is not turned off, and the Server service disconnects mapped
network drives after only a few seconds of idle time.

Also please refer link for server side configuration
http://support.microsoft.com/kb/128167/EN-US/

kbanerji@online.microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.
Rob Nicholson - 22 Dec 2004 15:07 GMT
> NOTE: If you set the autodisconnect value to 0 (zero), the autodisconnect
> feature is not turned off, and the Server service disconnects mapped
> network drives after only a few seconds of idle time.

Actually, we think it might have been EnableForcedLogoff in the same key
that's been causing the problem. I noticed that when comparing
lanmanagerserver parameters, the server that wasn't suffering from auto
disconnects by Win2K machines didn't have EnableForcedLogoff value whereas
the server that is disconnecting does have it.

We've deleted the value and so far, the Win2K PCs have not disconnected.

Cheers, Rob.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.