Operation Manual

Testing and Troubleshooting 237
If you do not see an incoming call on the system console, perform a
packet trace on the D channel to analyze the problem. For more
information on packet trace, refer to Chapter 18, "Monitoring ISDN
Connections."
If none of the tests is successful, contact your local PTT and have
them check your ISDN accesses.
If this does not help either, refer to section "Before Calling Technical
Support" at the end of this Chapter.
Problems with IPX
Network Protocol Errors
Inconsistencies in the configuration of the protocol-specific param-
eters (Protocol Parameters and/or Protocol Bindings) may cause
problems in the logical, protocol-specific connection handling.
These causes do not exclude each other. For example, an IPX connec-
tion to a remote router could not be established because a) the call has
been initiated to a Destination Subaddress that is not configured at
the remote router, which causes a problem in the ISDN-specific
connection handling and b) there are no IPX static routes and services
configured on the local router, which causes a problem in the logical,
IPX-specific connection handling.
For more information, see "Problems with IPX" below.
1. A connection to a remote router using IPX cannot be established
or a server on a remote LAN B is at first reported in LAN A, but
"disappears" after a certain time.
The most likely cause for this problem is that an IPX network number
exists twice in the WAN. The assigned network numbers for IPX (file
servers, LAN adapters) must be unique in the entire WAN. When
interconnecting separate LANs (as well as when locally adding new
segments to a LAN) for the first time, IPX network address conflicts,
resulting from inconsistencies in the IPX number assignment, fre-
quently occur.
Conflicts caused by inconsistencies in the IPX number assignments
will result in one of the following situations: