Troubleshooting Lost Network ConnectionsLast reviewed: November 21, 1994Article ID: Q90226 |
The information in this article applies to:
This article provides troubleshooting steps and suggestions that may assist you in solving network connectivity problems. Microsoft cannot guarantee the success of any specific steps provided in this article.
SUMMARYWindows for Workgroups may sometimes lose (drop) network connections. This problem is most likely to occur if one of the following conditions exists:
WARNING: If you lose your Windows for Workgroups connections, immediately save all open data files to backup files on your local drive or a remote drive where you still have a valid connection.
MORE INFORMATIONLoss of network connections can occur when you use any version of the redirector, but the basic redirector, invoked by using the "NET START BASIC" command, is most likely to have this problem. The problem seems to be caused by a timing issue in the NetBEUI protocol. It may also be related to the network buffer size because it occurs when data is being sent over the wire. In testing, this problem didn't occur unless the system was running under the conditions listed above; however, the problem may occur when a system is not under any stress, but this is very rare. Other factors that can cause connection problems include the following:
Attempting to RecoverTo determine if you have lost network connections, go to the server and use Net Watcher to see if the machine that is not responding still has a valid session open. This method does not always work because some applications can reopen the network connections. Some applications may not be affected by a lost network connection if they are not dependent on file pointers being maintained on the server. Sometimes you can issue the NET USE command at the command prompt to determine whether or not a session has been disconnected. This technique works best when the machine is not using a network installation (SETUP /N) of Windows. Issuing the DIR command may restore the network connection and allow the application to continue or at least exit without causing the system to stop responding (hang). You can also try to close all open files and attempt to quit Windows. If the problem results from a network installation of Windows having lost its network connections, you will get a message telling you that you do not have enough memory to complete the operation.
Avoiding the ProblemThe following steps may help prevent this problem:
|
KBCategory: kbnetwork kbtshoot
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |