There's a partial workaround, but it may not work 100% of the time: You can change how long Windows 2000 waits...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
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
This week, our expert answers the question of how to get DVD data off a disc, even if the user's PC doesn't have an optical drive.continue reading
This week, our expert answers a question on how to connect a phone or tablet to a USB drive with a micro-USB connector.continue reading
Open source and free suites such as LibreOffice and OpenOffice could save organizations money, but not effort in comparison with Microsoft Office.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.