Verifying remote network connectivity

If you can ping hosts on the local network, try to ping one remotely connected via a gateway or router:

• If ping returns an error indicating no route is available, and your system is not running a routing daemon such as routed, it is possible that the default router on your local subnet is not working correctly, or that your system has not been configured with the correct netmask and default router. Use the Network Configuration Manager to check that the TCP/IP configuration for each network adapter defines the correct netmask and default router for the network to which it is connected.

  See ``Adjusting your netmask to correct routing problems'' for more information about curing problems that can be caused by using an incorrect netmask. If necessary, you can reconfigure your system's routing table manually as described in ``Specifying a default router'' and route(1Mtcp).

• If ping fails completely, use traceroute(1Mtcp) to contact the remote host, and note where the failure occurs. If traceroute packets only reach a host within your network, you may need to perform troubleshooting on the last host reached. If they reach a destination outside your network, the problem is on the remote host. Contact the administrator of the remote host, if possible.