Page 529

Common Novell Troubleshooting Issues

497

interface Ethernet1

ip address 10.11.20.1 255.255.255.0

no keepalive

ipx network 2000

end

In this example, the router interface is displayed with the show ipx

interface

command, and the interface is FDDI with the default SNAP

frame type in use:

Router_A#show ipx interface

Fddi0 is up, line protocol is up

IPX address is 100000.0060.837c.4d31, SNAP [up] line-up,
RIPPQ: 0, SAPPQ: 0

In addition to frame type, a common issue with interconnectivity is incor-

rectly configured network addresses. All servers and routers on an IPX net-
work must be manually configured with the same external IPX network
number. A typical problem scenario occurs as follows:

After realizing that at least one server on the network is unreachable, the

administrator notes the following error on the router console or in the router
log. A similar message may appear on the server console:

00:60:08:40:1F:1C claims network 100 should be 200

In addition to confirming that the frame type of all network resources is

set to the same value, all servers and routers also need to have their external
IPX network numbers set to the same value. In this case, the unreachable
server is configured for IPX network 200, where the router has been config-
ured for network 100. After the correct network number is determined, the
incorrect setting should be modified.

Problems Attaching to Remote Servers

Frequently, IPX networks are designed without a locally attached server.
The file server may be installed on another local segment or may be remotely
connected via a serial connection.

www.sybex.com