TCP/IP problems communicating with a remote host

Edit online

If you cannot communicate with a remote host, try the these suggestions.

  • Run the ping command on the local host to verify that the local interface to the network is up and running.
  • Use the ping command for hosts and gateways that are progressively more hops from the local host to determine the point at which communication fails.

If you are having trouble with packet loss or are experiencing delays in packet delivery, try the following:

  • Use the trpt command to trace packets at the socket level.
  • Use the iptrace command to trace all protocol layers.

If you cannot communicate between a token-ring and an Ethernet network using a bridge, and you have verified that the bridge is good:

  • Check the MTU values of both adapters. The MTU values must be compatible to allow communication. A machine drops packets if the incoming packet (including headers) is greater than the adapter's MTU values. For instance, a 1500-byte packet sent over the bridge collects an 8-byte LLC header, making the total packet size 1508. If the receiving machine MTU is set to 1500, a packet of 1508 bytes is dropped.