User Guide

236 Chapter 7. Troubleshooting
Problems Accessing the Remote Network
Bridging
• Make sure to reboot if you have made any bridging destination or control changes.
• All IP addresses must be in the same IP subnetwork (IP is being bridged).
• Check that a bridging default destination has been configured and is enabled.
• Be sure to reboot if the bridging destination or status has been changed.
• Check that bridging is enabled locally (use the
remote listBridge
command).
• Verify that bridging is enabled by the remote router (use the
remote list
command).
• Verify that the authentication passwords are correct.
• Reboot your PC if you have Windows for WorkGroups.
• In Windows 95, do not forget to declare shared disk directories. Check the sharing properties on your
C:
drive
.
• In the Terminal Window, check that calls are answered from the remote router.
• Check also for any PAP/CHAP errors for the remote router.
TCP/IP Routing
• Check that Ethernet LAN TCP/IP Routing has been enabled (
eth list
command).
• The IP addresses of the local and remote networks belong to different IP subnetworks.
• Make sure that there is an existing route to the remote network.
• Make sure that there is a route back from the remote network.
• There must be a source WAN IP address defined if you are using NAT.
• Check that, if required, the source and remote WAN IP addresses are on the same subnetwork
• Reboot if you have made any IP address or control or protocol option changes.
• Check that the IP address of the station/network connected to the LAN beyond the remote router is
correct, as well as the associated subnet mask.
• If the remote router WAN IP address and subnet mask are required, check that they have been specified
correctly.
• Check that a default route has been specified, if needed.
• Be sure to reboot if IP addresses or control or protocol option changes have been made.
• Check that you are using an Ethernet cable.
• Check that IP routing is enabled at both ends.
• The IP address must be within the valid range for the subnet.
• Verify that the IP and gateway addresses are correct on the PC.