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.