Windows for Workgroups may sometimes lose or drop network connections. This issue is most likely to occur if one of the following conditions exists:
1. You are running a network installation (SETUP /N) of Windows for Workgroups.
NOTE: Microsoft does not recommend running Windows for Workgroups from a network installation (SETUP /N) because doing so is a common stress condition that can cause a loss of network connections.
If a system is run this way, store data and applications on a client or server that does NOT contain the shared Windows directory (created with SETUP/A); this appears to reduce the frequency of the issue.
2. Several people in a workgroup are running the same application from a server.
NOTE: Network connections also can be lost when many people run the same application from a server (for example, 10 clients use the same installation of FileMaker Pro). Windows-based applications generally report segment load failures when the network connection is lost. If network connections are lost or dropped, the system or application may stop responding(hang), or the network installation of Windows for Workgroups may become corrupted.
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.
Why it happens?
---------------------------
Loss 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 issue. The issue 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.
Other factors that can cause connection issues include the following:
- Network cards: Some network cards are more prone to these issues than others.
- Machine speed: The slower the machine, the more likely that its network connections may be lost.
This issue usually originates with the server but affects clients only.
Troubleshooting
----------------------------
The following steps may help prevent this issue:
- Increase FILES= to 128 or higher in the CONFIG.SYS file.
- Increase FCBS= to 25 or higher in the CONFIG.SYS file.
- Increase Sessions= to 32 or higher in the PROTOCOL.INI file.
- Set NCBS= to 64 in the PROTOCOL.INI file.
- Set NetHeapSize= to 52 in the [386Enh] section of the SYSTEM.INI file.
- Set TimerCriticalSection= to 10000 or higher in the [386Enh] section of the SYSTEM.INI file.
- If you are using a network installation of Windows (Setup /N) set maintainserverlist= to NO in the [network] section of the SYSTEM.INI file.