There's a partial workaround, but it may not work 100% of the time: You can change how long Windows 2000 waits...
before it considers a connection idle and disconnects it, which may allow more clients to access the system so long as they don't all attempt to do so at once.
To do this, use the net command: net config server /autodisconnect: [timeout], where [timeout] is a value in minutes. If you set it to 0, the disconnect happens in a matter of seconds, which may help alleviate the problem to a high degree although not solve it. You can also edit the Registry directly to affect this. In HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters, create or edit the DWORD AutoDisconnect and set it to the value in minutes to use. If you set it to 0, again, the disconnect will take place in a few seconds.
Using a value of -1 for either of these will cause client connections to persist indefinitely.
Dig Deeper on Windows File Management
Related Q&A from Serdar Yegulalp, Contributor
Mulling over an upgrade to Windows Server 2012? You're bound to have some questions. Our expert answers the most common ones.continue reading
The more information you want about Hyper-V traffic, the harder it will be to get. Our expert explains why things will get better in Windows Server 8.continue reading
There are several potential reasons why your users’ Outlook passwords for Exchange are not being stored. Our expert examines the top four and their ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.