Ping your own server

Ping the local interface to test whether packets can reach interfaces on your local area network (LAN).

For IPv4, this is the IP address of a manually configured interface. For IPv6, this is the IP address of an automatically configured interface or a manually configured interface. It is also useful to ping an interface that is beyond your local server but attached to the LAN.

To ping your own server to troubleshoot the problem, follow these steps:

  1. 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
    Ping parameters can be used to 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.
  2. Failures might indicate the following problems.
    Problem Recovery
    The TCP/IP stack has not been activated on your server. At the command line, type STRTCP to start the stack.
    The local host table does not have an entry for the IPv4 host name and IP address.
    You need to add the entry to the host table. This is only relevant for IPv4 because host tables do not currently support IPv6. To verify the host table entries, follow these steps:
    1. At the command line, type CFGTCP (Configure TCP/IP).
    2. Select option 10 (Work with TCP/IP Host Table Entries).
    3. Verify that the host table contains an entry for the host name and IP address.
    Your line description or local interface has not been properly configured. The line should be varied on, and the interface should be started.
    If you are using IPv6, the IPv6 stack has not been activated on your server. You can start IPv6 by specifying *YES for the STRIP6 parameter on the STRTCP (Start TCP/IP) command. If TCP/IP has already been started, you will need to end and restart TCP/IP. At the command line, type ENDTCP (End TCP/IP) to end TCP/IP. To restart TCP/IP and the IPv6 stack, type STRTCP STRIP6(*YES) at the command line.
    Note: Through ending TCP/IP, you end all Telnet sessions and all TCP/IP servers that are running.
Related reference
Ping parameters