System information

Troubleshooting XNS
Book Title
14-304
This section covers the most common network issues in XNS environments:
XNS: Clients Cannot Connect to Servers over Router
XNS: XNS Broadcast Packets Not Forwarded by Router
XNS: Clients Cannot Connect to Server over PSN
XNS: Clients Cannot Connect to Servers over Router
Symptom: Clients cannot make connections to XNS servers across a router. Clients might be able
to connect to servers on their directly connected networks.
Table 14-1 outlines the problems that might cause this symptom and describes solutions to those
problems.
Table 14-1 XNS: Clients Cannot Connect to Servers over Router (continued)
Possible Problem Solution
Router interface is
down
Step 1 Use the show interfaces exec command to check the status of the router
interfaces.
Step 2 If the status line indicates that an interface that should be up is “administratively
down,” use the no shutdown interface configuration command on the interface.
Step 3 If the status line indicates that the interface or line protocol is in any other state,
refer to the chapter that discusses your media type.
Hardware or
media problem
For information on troubleshooting hardware problems, see the chapter that discusses your
media type. For information on troubleshooting media problems, see Chapter 15,
“Troubleshooting Serial Line Problems.
XNS routing is not
enabled on router
Step 1 Use the show running-config privileged exec command to view the router
configuration. Check whether XNS routing is enabled on the router.
Step 2 If XNS routing is not enabled, add the xns routing router configuration command
and related commands as necessary.
Example:
This example starts XNS routing and assigns XNS network numbers to the
physical networks connected to two of the router’s Ethernet interfaces:
xns routing
interface ethernet 0
xns network 20
interface ethernet 1
xns network 21
For more information on configuring XNS routing, see the Network Protocols
Configuration Guide, Part 2.
Mismatched router
network number
If the network number specified on the router is different from that configured on XNS
servers, RIP
1
is not able to forward traffic correctly.
Step 1 Check the network numbers of network servers.The local XNS server
administrator provides the server network numbers.
Step 2 Use the show xns interface exec command to obtain the network number
specified on the server side of the router.