Novell NETWARE 6-DOCUMENTATION Manual page 1854

Services Are Inaccessible in the Area
malfunctioning link between the two networks. To determine which link
has the problem, refer to
Cause 3 —There is a duplicate network number. This can cause a
duplicate system ID, provided that both systems are in the same area and
the duplicate network numbers are two internal network numbers on two
NetWare implementations of NLSP. The console probably displays the
following message:
System server_name
has my system ID in it.
Change the internal network number of one of the conflicting systems, or
remove one of the systems from the network immediately. For
information about how to find the malfunctioning node, refer to
Connectivity Problems (Duplicate ID or Network Number)" on page
Cause 4 —Packet filtering has been implemented on a router. This can
cause symptoms similar to those caused by duplicate network numbers
(for example, network A might be visible from network B, but network B
is not visible from network A).
If communication does not occur within an NLSP area, it is usually easy
to determine whether the network fault is caused by packet filtering or a
duplicate network number. Use IPXCON to view duplicate LAN network
numbers (parameter path: Select NLSP Information > LANs). If your
system does not have a matching network number, use FILTCFG to
remove the packet filtering.
Services are inaccessible in the area.
Cause 1 —Services are being blocked by filters.
Examine the IPXCON Services option of each router in the path to isolate the
router that is filtering the services.
Cause 2 —Network connectivity problems.
Check that the network to which the service is attached exists. If the network
does not exit, look for link connectivity in the path between the area in the
network that is missing the network number and the area that is generating the
service.
"Applications Perform Poorly" on page
with internal network number number
147.
"IPX
129.
Troubleshooting 143