Hallo Wissende,
an meinem Heimnetzwerk, zwei PC’s mit W2k professional, verschwindet an einem immer wieder die Netzwerkverbindung: Wenn ich über Netzwerkumgebung oder den Explorer zugreifen will, erscheint die Meldung: Netzwerkpfad nicht gefunden. Nach einem Neustart funktioniert die Verbindung wieder. Die Kontrolllämpchen am Hub stehen alle auf grün, die verkabelung sollte in Ordnung sein.
MFG Peter
Hi Peter,
an der Dos-Shell mal an beiden PCs
net config server /autodisconnect:720 eingeben.
Das sollte dein Laufwerk nach 12 h trennen. Laut Microsoft sollte der Wert -1 dauerhaft nicht getrennt werden aber das funzt nicht.
Gruss Buck
Hallo Buck,
sehr informativ. Weißt Du auch wo das in der registrierung drin steht? Kann man das ganze nicht auch dort ändern?
Gruß
DJ
[Bei dieser Antwort wurde das Vollzitat nachträglich automatisiert entfernt]
Hi Jens,
keine Ahnung, der Wert steht aber auch in der lokalen Sicherheitsrichtlinie. Kannst ja mal suchen vielleicht findest Du es ja.
Gruss Buck
Hi,
jetzt war ich noch mal ganz fleissig.
Microsoft Knowledge Base Article - 138365
How Autodisconnect Works in Windows NT and Windows 2000
MORE INFORMATION
You can find the LAN Autodisconnect parameter in the registry under the subtree HKEY_LOCAL_MACHINE under the subkey:
\System\CurrentControlSet\Services\LanmanServer\Parameters
NOTE: The preceding entry must be located on the computer that has the share or shares.
The purpose is to disconnect idle sessions after a set number of minutes. The number of minutes can be set at a command prompt using the net config server command.
For example, to set the Autodisconnect value to 30 minutes, you would run the following command line:
net config server /autodisconnect:30
The valid value range is -1 to 65535 minutes at the command line. To disable Autodisconnect set it to -1.
Setting Autodisconnect to 0 does not turn it off and results in very fast disconnects, within a few seconds of idle time. (However, the RAS Autodisconnect parameter is turned off if you set it to a value of 0.)
NOTES:
It is preferable to modify the LAN Autodisconnect directly in the registry. If you modify it at the command line, Windows NT and Windows 2000 may turn off its autotuning functions. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
128167 Server Service Configuration and Tuning
The valid value range if you edit the LAN Autodisconnect parameter in the registry is 0 to 4294967295 (Oxffffffff).
For a Windows 2000 Server in a Domain, running either as a domain controller or as a server, the maximum value is 65,535 (0xffff). Values set above this will be returned to 0xffff after policy refresh. Windows 2000 Servers in a workgroup may be set to any value as indicated.
If you configure the Autodisconnect option to -1 at the command prompt, Autodisconnect is set to the upper value in the registry. This is approximately 8,171 years (not tested), which should be long enough to be the equivalent of turning Autodisconnect off.
The registry does not allow you to add a -1 value. However, that modification may be made at the command prompt with the following command:
net config server /autodisconnect:-1
When this is set, two additional registry keys are added:
anndelta: REG_DWORD: 0xbb8
announce: REG_DWORD: 0xf0
Announce: Specifies the network announce rate, in seconds. This rate determines how often the server is announced to other computers on the network.
Anndelta: Specifies the delta value for the announce rate, in milliseconds. This value specifies how much the announce rate can vary from the period of time specified in the announce member.
The delta value allows randomly varied announce rates. For example, if the announce member has the value 10 and the anndelta member has the value 1, the announce rate can vary from 9.999 seconds to 10.001 seconds.
After a few minutes of idle time, your mapped drive or drives may be disconnected, and a red „X“ may appear next to the mapped drives in Windows Explorer.For additional information, click the article number below to view the article in the Microsoft Knowledge Base: