Novell NETWARE 6-DOCUMENTATION Manual page 1851

An NLSP Server on a LAN Cannot Be Accessed
140 Internetwork Packet Exchange
If the link is corrupting data, the corrupt LSPs statistic increases. To check
this, load IPXCON (parameter path: Select NLSP Information > System
Information > Detailed NLSP System Information). Even a single corrupt LSP
indicates a serious problem because LSPs are transmitted infrequently. Note
that this counter is a global counter and it is possible that some other media is
corrupting the data link.
You cannot access a server on the LAN.
Cause 1 —Area address is set to the wrong value.
In this case, the number of destinations (known networks and services)
implies local connectivity only. Also, the Initialization Failures statistic in
IPXCON increases (parameter path: Select Circuits > Detailed Circuit
Information). If you have configured area addresses, make sure that all
systems that should be in communication have the same area addresses.
It is acceptable for systems to have different addresses, if that is the
desired configuration.
Cause 2 —RIP is not enabled.
If you are running multiple areas on a LAN and are using RIP to
interconnect the systems, verify that RIP is enabled on those servers that
are interconnecting areas. Load NIASCFG and select Configure NIAS >
Protocol and Routing > Bindings > IPX Binding > Expert Bind Options
> RIP Bind Options > RIP State. If the RIP State is set to Auto in
NIASCFG, there is a small chance that RIP will fail. To avoid having RIP
fail, set RIP State to On.
Cause 3 —Hub or bridge has failed.
Use IPXPING to check whether there is data-link connectivity.
Cause 4 —LAN board driver does not support multicast, even though the
driver's documentation claims that it does.
Use a driver that supports multicast or set the MAC Channel option to
Broadcast (parameter path: Select Bindings > a specific binding > Expert
Bind Options > NLSP Bind Options).
Cause 5 —LAN board has failed. This system does not see other systems
on a LAN, or it does not have any adjacencies in the Up state. However,
it declares itself as being attached to the LAN.