[table of contents][main topic of chapter][index][previous][next]
[copyright and trademarks][Preface Overview][Cisco TCP/IP Suite books]

Testing Your Network Connection

If your workstation does not communicate on the network as expected, you can use Ping to test Cisco TCP/IP Suite and network communications. Your network administrator may be able to provide additional assistance.

The Ping application tests network connections by sending ICMP (Internet Control Message Protocol) echo requests to a target host and then waiting for replies. When testing a connection, Ping tracks the number of packets sent, the number of replies received, the percentage of packets lost, and the amount of time required for the packets to reach the destination and for replies to be received. This information lets you verify that your workstation can communicate with other hosts and that no information has been lost.

To start Ping, choose Ping from the Cisco Suite 100 group on the Start menu, or double-click the Ping icon in the Cisco Suite 100 program group. As an alternative, you can start MultiNet Tools and click the Ping tab.

Note

Firewalls often allow Ping to work but not other services such as Telnet or FTP. You may have to contact the network administrator for the remote host for assistance.

See the online help for more information about how to use Ping.

This section includes:

Pinging Your Workstation by Loopback Address

To verify that your workstation can receive and send responses, and that Cisco TCP/IP Suite is operating correctly, use Ping with the special loopback address 127.0.0.1.

If the Ping session is not successful:

  1. Make sure Cisco TCP/IP Suite was installed correctly.
  2. Call Technical Support.

Pinging Your Workstation by IP Address

To verify that your workstation's network interface card and driver are working correctly, start Ping and Ping your workstation by IP address.

If the Ping session is not successful:

  1. Verify that the network adapter is configured correctly for your workstation.
  2. Use the Configuration Utility to verify that your workstation's IP address and subnet mask are correct.

Pinging Your Network's Broadcast Address

To verify that your workstation's TCP/IP stack is successfully communicating with the network, start Ping and Ping your network's broadcast address. When pinging your network's broadcast address, all other nodes using the same broadcast address should respond.

If the Ping session is not successful:

  1. Verify that your workstation is plugged into the network.
  2. Use the Configuration Utility to verify that your workstation's IP address and subnet mask are correct.
  3. Verify that you are using the correct broadcast address.
  4. Verify that you are on the same network as the other hosts.
  5. Verify that an Ethernet or Token-Ring interface is enabled.

Pinging Your Workstation by Name

To verify that host names are being resolved to IP addresses correctly, Ping your workstation by host name.

If the Ping session is not successful:

  1. Verify your workstation is securely attached to the network.
  2. Use the Configuration Utility to verify that your workstation's host name and domain name are correct.
  3. If your workstation uses DNS to resolve names, use the Configuration Utility to verify that the IP address of the DNS server is correct.
  4. If your workstation uses DNS, ping the DNS server by IP address to verify the DNS server is running and available.
  5. If your workstation uses a host table to resolve names, use the Configuration Utility to verify that your workstation's host name and IP address are correct.

Pinging Another Workstation by IP Address

To verify that your workstation can communicate with other systems on the local network, Ping another local system by IP address.

If the Ping session is not successful:

  1. Verify the other system is securely attached to the network and is running.
  2. Verify you are using the correct IP address for the other system.

Pinging Another Workstation by Name

To verify that your workstation can communicate with other systems on the local network by name, Ping another, local system by host name.

If the Ping session is not successful:

  1. Verify you entered the host name correctly.
  2. Verify the other machine is running and securely attached to the network.
  3. If your workstation uses DNS to resolve names, use the Configuration Utility to confirm that the IP address of the DNS server is correct.
  4. If your workstation uses DNS, Ping the DNS server by IP address to verify it is running and available.
  5. If your workstation uses a host table to resolve names, use the Configuration Utility to verify that the host name and IP address of the other system are correct in the host table.

Pinging a Remote System by IP Address

To verify that your workstation can communicate with other hosts on the Internet, Ping a remote host by IP address.

If the Ping session is not successful:

  1. Use the Configuration Utility to verify that the IP address of the default route is correct.
  2. Verify that the remote host is running and securely attached to the network.
  3. Use MultiNet Tools TraceRoute to determine where the failure occurs.

Pinging a Remote System by Name

To verify that your workstation can communicate with other hosts on the Internet by name, Ping a remote host by name.

If the Ping session is not successful:

  1. Verify you entered the host name correctly.
  2. Verify the other machine is running and securely attached to the network.
  3. If your workstation uses DNS to resolve names, use the Configuration Utility to confirm that the IP address of the DNS server is correct.
  4. If you workstation uses DNS, Ping the DNS server by IP address to verify it is running and available.
  5. If your workstation uses a host table to resolve names, use the Configuration Utility to verify that the host name and IP address of the other system are correct in the host table.
  6. Use the Configuration Utility to verify that the IP address of the default route is correct.
  7. Use MultiNet Tools TraceRoute to determine where the failure occurs.



[table of contents][main topic of chapter][index][previous][next]
[copyright and trademarks][Preface Overview][Cisco TCP/IP Suite books]

Copyright© 1995-1996 Cisco Systems, Inc. All Rights Reserved.

HTML file generated May 15, 1996.