System information

Troubleshooting XNS 14-305
XNS: Clients Cannot Connect to Servers over Router
Mismatched router
network number
Step 3 Compare the network numbers. If they do not match, reconfigure the router or the
server, as appropriate, with the correct network number. To reconfigure the router,
use the following command:
xns network number
The argument number is the network number, in decimal format. Every XNS
interface in a system must have a unique XNS network number.
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
Step 4
If the network numbers match, check the router interface on the client side and
make sure that the assigned network number is unique with respect to all network
numbers in the XNS internetwork.
Misconfigured
access list
Step 1 Use the show xns access-list privileged exec command on routers in the path
from source to destination. This command shows whether there are access lists
configured on the router.
Step 2 Disable all access lists that are configured on the router using the no xns
access-group command.
Step 3 Test the connection from the client to the server to see whether connections are
now possible. If the connection is successful, an access list is blocking traffic.
Step 4 To isolate the problem access list, apply one access list statement at a time until
you can no longer create connections.
Step 5 When the problem list is identified, alter it so that necessary traffic is allowed to
pass. Configure explicit permit statements for traffic that you want to be
forwarded by the router.
Step 6 If problems persist, continue testing for problem access lists on all routers in the
path from source to destination.
Possible Problem Solution