Specifications

Chapter 7. Troubleshooting 173
¥ The IP address must be within the valid range for the subnet.
¥ Verify that the IP and gateway addresses are correct on the PC.
¥ Windows 95 may remember MAC addresses: if you have changed MAC addresses, reboot the router and
the PC.
¥ In Windows 3.1., check that the TCP driver is installed correctly. Ping (ping command) your PCÕs IP
address from the PC. Successful ÒpingingÓ results let you know that the TCP driver is working properly.
¥ If you have changed an IP address to map to a different MAC device, and ping or IP fails, reboot your
PC.
¥ Use the iproutes command (page 191) to verify which routerÕs name is the default gateway (this cannot
be 0.0.0.0).
IPX Routing
¥ Check that IPX routing has been enabled and that the remote end is enabled for IPX routing.
¥ Validate that the IPX WAN network number matches the remote routerÕs WAN network number.
¥ Check that IPX SAPs correctly identify the servers and applications on the remote network and have
valid network numbers, node numbers, etc.
¥ Check that every SAP has a router to its internal network.
¥ Check that the IPX routes (network numbers, hops, and ticks) seeded into the routing table for network
segments and servers beyond the remote router are correct.
¥ Validate that the IPX WAN network number matches the remote routerÕs WAN network number.
¥ Check that the IPX routes (network numbers, hops, and ticks) seeded into the routing table for network
segments and servers beyond the remote router are correct.
¥ Check that IPX SAPs correctly identify the servers and applications on the remote network and have
valid network numbers, node numbers, etc.
¥ Be sure to reboot if IPX addresses, routes, SAPs or control has been changed.
¥ If the router fails to negotiate IPX:
¥ Make sure that at least one WAN number is not equal to zero at one end of the link.
¥ The server must have an IPX route to the remote LAN.
¥ The Novell server needs to have
burst mode turned on.
¥ Large Internet packets have to be turned on.
¥ For Novell 3.12 and later:
¥ Client needs VLM.EXE, net.cfg: large Internet packets=ON, Pburst=5
¥ If you canÕt see the server SAPs:
¥ Check the frame types using the eth list command (page 248) and ensure that they are the same on
both routers.
¥ Check that the Ethernet cable is correctly plugged in.