TCP/IP Troubleshooting Tools
Network command-line utilities included with computer operating systems help you quickly identify the source of a network disconnect, saving you time and money. From the command line, you can identify failure points among network path components such as network adapters, the local network gateway, a router, remote hosts, and programs and services. Widely available TCP/IP command-line utilities can reveal a disconnect or performance root cause without the expensive diagnostic tool price tag.
Other People Are Reading
-
Windows IPConfig
-
The IPConfig command-line utility reveals the current TCP/IP configuration assigned to each network interface. Typing “ipconfig /all” at the command prompt reveals important TCP/IP parameters you must know for troubleshooting such as network adapter IP address, subnet mask, gateway IP address and DNS server IP address, as well as whether the Dynamic Host Configuration Protocol is enabled. If the displayed TCP/IP configuration parameters are compatible with the network, you can use them with other TCP/IP troubleshooting tools for further investigation.
Ping
-
The Ping command-line utility tests network connectivity between a computer and another device on the network. Typing “ping 127.0.0.1” at the command prompt ranks as a first step to verify that the computer TCP/IP stack is functional. Pinging the computer network adapter's IP address reveals that the network adapter is working correctly, while pinging the network gateway IP address verifies connectivity with the network router or gateway. Pinging the IP address of an Internet host determines if it is reachable and available.
-
Trace Route
-
The Trace Route or Tracert tool verifies network connectivity along a specific path. After typing “tracert” at the command prompt, followed by a network host IP address, you'll see the IP address and response time of each device that forms the network path. The Trace Route tool sends an ICMP or Internet Control Message Protocol echo packet to each network path device, which then send reply packets with information displayed in the command-line output. If a network path device -- other than a firewall or bridge -- doesn't send a reply, it may be causing the network performance issues or disconnects.
Netstat
-
The Netstat command-line utility displays all TCP/IP established connections and reveals which programs and services are configured to receive network communication. Typing “netstat –ab” at the command prompt displays a list of established TCP/IP connections and the name of the program or service providing the connection. Netstat determines if a service or program is ready to accept or has accepted connections, along with the hostname and IP address associated with each established connection.
-
References
- Photo Credit Ablestock.com/AbleStock.com/Getty Images
