Why Windows NT Cycles Through Persistent Connections

 Last reviewed: April 4, 1997
Article ID: Q101831

The information in this article applies to:
  • Microsoft Windows NT operating system, version 3.1
  • Microsoft Windows NT Advanced Server, version 3.1

After logon, Windows NT may repeatedly cycle through connecting to your persistent network connections if you have several transports loaded. This occurs with either a standard logon to a local account or with AutoAdminLogon enabled.

Windows NT attempts to restore the network connections before the network is started. The system waits for the network to start up, but, in order to make the system more responsive, it only waits for a maximum of 15 seconds. If there are several protocols loaded, then Windows NT will retry the connections until the network actually starts and it can reconnect.

Additional query words: prodnt long delay problem
Keywords : kbnetwork ntnetserv
Version : 3.1
Platform : WinNT

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 4, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.