Novell NETWARE 6-DOCUMENTATION Manual page 1848

Cause 3 —System misconfiguration.
By default, NLSP timers are set so that a system becomes unreachable when
three packets are dropped. Look at the system's configuration to ensure that
this setting has been used.
Cause 4 —One or both of the systems are dropping packets.
Check the interface boards to determine whether packets are being dropped
because of insufficient Event Control Blocks (ECBs). Increasing the
maximum number of physical receive packets might help stop the system
from dropping packets. To reach this option load install, select NCF file
options > edit startup.ncf. Increase the maximum number of physical receive
packets to at least 1524. However, the system might be incapable of handling
the system load. In this case, increase the processor power of the system that
is dropping packets, or reduce the load on the server by either removing NLM
files or decreasing the number of users on the system. You can determine
whether the system is using too much CPU processing power by using
MONITOR and viewing utilization.
Cause 5 —NLM on the server is not relinquishing control of the CPU
frequently enough.
This is a rare occurrence. To determine whether this is occurring, select
Performance in MONITOR. Look for processes that exceed many millions of
cycles per iteration. You can also determine that an NLM is malfunctioning by
removing the NLM from the server and observing whether the problem is
resolved.
Cause 6 —Internal error in NLSP.
If you have exhausted all other possibilities, you should document your
system configuration, number of users, and error frequency and send a copy
of the system configuration (SYS: SYSTEM\CONFIG.TXT), including the
NLSP configuration file (usually located in \ETC\NLSP.CFG), to technical
support.
Troubleshooting 137