5 replies
Okay, this will include a registry edit. Here is the ususal caution on editing the registry. Back it up before making any changes.
1. On the server, open up the properties to the share, select sharing, then click on the 'caching' button near the bottom. Turn off all caching.
2.Open the registry using 'regedit'. Go to the following key......
HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
Add or edit the following item...
Value Name: CachedOpenLimit
Data Type: REG_DWORD
Data: 0 (the default is 5) Change it to 0 (zero)
Add or edit the following item...
Value Name: OplocksDisabled
Data Type: REG_DWORD
Data: 0 (zero)
3. from a command prompt, type the following....
net config server /autodisconnect:-1
(between 'autodisconnect' and '-1' is a colon. It sometimes does not show up in these QA screens.
Reboot your server. This should take care of your problem. Please let me know the results.
Best of luck
by brian
This seems to be fairly common. Most others compain that the disconnect is to soon but either way it is fixed using the same techniques. The following questions have information that explain how to adjust the time to disconnect.
https://www.techrepublic.com
/forumqa/thread_detail.jhtml?thread_id=80200
https://www.techrepublic.com
/forumqa/thread_detail.jhtml?thread_id=67169
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending