asked on

Network: Lose connectivity

Have 2-computers(connected Peer-to-Peer). Often, they lose connectivity(ie. NetworkNeighborhood/WorkGroup, DOESNT shows the other computer). I have to restart both the machines to restore connectivity.

In other office, 2-machines are connected thru a hub, still same problem.

At my previous employer, the machines were plugged into LAN-jack, and NEVER have connectivity problems.

Solution needed....

ASKER CERTIFIED SOLUTION

toshie

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Falco Bethke

go to the properties of your NIC.
in "Power Management" uncheck the checkbox "Allow the computer to turn off this device to save power"

from the KB:
Q138365
The information in this article applies to:

- Microsoft Windows NT Workstation versions 3.5, 3.51, 4.0
- Microsoft Windows NT Server versions 3.5, 3.51, 4.0
- Microsoft Windows 2000 Professional
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server

SUMMARY

This article documents the Windows NT local area network (LAN) related
Autodisconnect parameter.

Windows NT uses two different Autodisconnect parameters; one for disconnecting
Remote Access Service (RAS) connections and another for disconnecting LAN
connections. The RAS Autodisconnect parameter is documented in the Microsoft
Knowledge Base article Q153944, but the LAN version is undocumented. The only
published reference to this Autodisconnect is in the Windows NT Resource Kit NT
Registry Entries help file, in an overview of entries for the LanmanServer
Parameters section.

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

Purpose: The function 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:

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.)

NOTE: It is preferable to modify the LAN Autodisconnect directly in the registry.
If you modify it at the command line, Windows NT may turn off its autotuning
functions. For additional information, please see the following article in the
Microsoft Knowledge Base:

ARTICLE-ID: Q128167
TITLE : Server Service Configuration and Tuning

The valid value range if you edit the LAN Autodisconnect parameter in the
registry is 0 to 4294967295 (Oxffffffff). 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.

NOTE:The registry does not allow you to add a -1 value, however, that
modification may be made at the cmd prompt with the following command:

"net config server /autodisconnect:-1" (without the quotation marks)

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.

Moondancer

Netminder

Admin notified of User neglect. Force-accepted by
Netminder
Community Support Moderator
Experts Exchange