Operation Manual

238 NetWare MultiProtocol Router for ISDN 3.1 Installation and ISDN Configuration Guide
- An IPX-connection over ISDN cannot be established between two
networks although the ISDN-specific connection handling works
properly.
- A server on a remote LAN B is at first reported in LAN A (e.g. by
SLIST), but “disappears” after a certain time.
- A copy operation is successful from LAN A to LAN B, but not
from LAN B to LAN A. (This situation might also be caused by
incorrect packet size settings, see 3. below)
Solution:
Check IPX Network Numbers and , if you are dialing a NetWare
MultiProtocol Router for ISDN 3.1, whether “set force rip/sap up-
dates” is set to “on”.
The network numbers and internal network numbers assigned for
IPX must be unique throughout the WAN; i.e. you must not assign
the same address twice. This restriction often leads to one or more
address conflicts when individual LANs are first connected, or when
new segments are added to a LAN.
2. A copy operation is successful from LAN A to LAN B, but not
from LAN B to LAN A.
A collision problem might exist between the configured IPX network
numbers.
Solution:
Check the assignment of IPX network numbers configured for incon-
sistencies, all numbers must be unique in the whole WAN.
Novell has developed a special “Network Registry Program” to perform the
task of assigning IPX numbers. If you are interested in this program, contact
Novell at [phone] (phone) or [phone] (fax).
Suggestion
Problems with TCP/IP
If you are running FTP, you might see the following warning mes-
sages on the system console:
CANNOT START SYS:ETC\NET\NETWARE\SERVICES
NETDIR_GET BY NAME:N2A:SERVICE NAME NOT FOUND
CANNOT MAP TO TCP