Ping a remote interface to test whether packets can leave your
network and reach a remote system. Ping a remote Domain Name System (DNS)
to make sure your server can resolve domain names.
- At the command line, type these commands:
- For IPv4: PING 'nnn.nnn.nnn.nnn' or PING hostname
- For IPv6: PING 'x:x:x:x:x:x:x:x' or PING hostname
See Ping parameters to fine-tune the Ping command to get the most accurate
results. Prompt on the Ping command by selecting F4 for complete details on
the Ping parameters.
- Failures might indicate the following problems:
- TCP/IP has not been started. To start TCP/IP, type STRTCP (Start
TCP/IP) at the command line.
- 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.