Ping the interface on a network not directly attached to your local network

Ping the remote interface to test whether packets can leave your network and reach a remote system.

1. In iSeries™ Navigator, expand your iSeries server > Network.
2. Right-click TCP/IP Configuration, and select Utilities > Ping.
3. Specify the IP address or host name of a remote interface. If you are testing by using the host name, you must select the Protocol for host names.
4. Click Ping Now to send the Ping. View the responses to your Ping in the list of results.
5. Failures might indicate the following problems:
   • TCP/IP has not been started.
   • The remote system is not available.
   • A frame size problem. The frame size on the line description should be greater than or equal to the maximum transmission unit (MTU) of the interface.
   • A network, router, next hop, or bridge problem.
   • The default route is not configured on your server.
   • The remote system or intermediate firewall has ICMP Echo Requests or Replies disabled.
   • If you have multiple IP addresses and subnets, make sure that IP datagram forwarding is set to *YES.
   • If the interface you are trying to reach is configured to an Ethernet adapter, you might need to change the Ethernet standard in the Ethernet line description. Specify either the correct Ethernet standard or *ALL.
   • A DNS or host name table problem. For example, if the Ping works for the interface's IP address but not the host or domain name, you need to check your host table or DNS entries.