Skip to content
My Docs

Ping And Connectivity Testing

Category: Network Tools and Commands
Type: Network Tools & Commands
Generated on: 2025-07-10 09:13:06
For: Network Engineering, Administration & Technical Interviews

1. Tool Overview

  • Ping (Packet Internet Groper): Verifies IP-level connectivity to a host. Measures round-trip time (RTT) and packet loss. Essential for basic network troubleshooting.
  • Traceroute/Tracert: Maps the path packets take to reach a destination, identifying routers along the way. Useful for pinpointing network bottlenecks or failures.
  • Pathping (Windows): Combines ping and traceroute functionality, providing packet loss statistics at each hop along the path. More comprehensive than traceroute.
  • Nmap (Network Mapper): Powerful network exploration and security auditing tool. While not solely for connectivity, it can identify open ports, services, and OS information, aiding in connectivity troubleshooting.
  • Netcat (nc): Versatile tool for reading and writing data across network connections. Useful for testing port availability and basic service communication.
  • dig (Domain Information Groper): Queries DNS servers for information about domain names. Important for verifying DNS resolution, which is crucial for connectivity.
  • nslookup: (Deprecated but still in use) Similar to dig, but with a simpler interface.
  • Telnet: (Avoid in production) Can be used for basic connectivity testing to a specific port. Highly insecure, avoid for sensitive data.
  • Test-NetConnection (PowerShell): Windows specific, tests TCP connectivity and DNS resolution.

2. Basic Syntax

  • Ping:
    • Linux/macOS: ping [options] <hostname_or_IP>
    • Windows: ping [options] <hostname_or_IP>
  • Traceroute/Tracert:
    • Linux/macOS: traceroute [options] <hostname_or_IP>
    • Windows: tracert [options] <hostname_or_IP>
  • Pathping (Windows): pathping [options] <hostname_or_IP>
  • Nmap: nmap [options] <hostname_or_IP_or_Network>
  • Netcat: nc [options] <hostname_or_IP> <port>
  • dig: dig [options] <domain_name> [query_type]
  • nslookup: nslookup <domain_name> [server]
  • Telnet: telnet <hostname_or_IP> <port>
  • Test-NetConnection (PowerShell): Test-NetConnection <hostname_or_IP> [-Port <port>]

3. Practical Examples

  • Basic Ping:

    Terminal window
    # Linux/macOS/Windows
    ping google.com
    PING google.com (142.250.185.142) 56(84) bytes of data.
    64 bytes from fra16s36-in-f14.1e100.net (142.250.185.142): icmp_seq=1 ttl=118 time=7.58 ms
    64 bytes from fra16s36-in-f14.1e100.net (142.250.185.142): icmp_seq=2 ttl=118 time=7.55 ms
    64 bytes from fra16s36-in-f14.1e100.net (142.250.185.142): icmp_seq=3 ttl=118 time=7.58 ms
    ^C
    --- google.com ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 2003ms
    rtt min/avg/max/mdev = 7.551/7.571/7.585/0.014 ms

  • Traceroute to Google:

    Terminal window
    # Linux/macOS
    traceroute google.com
    

    # Windows
    tracert google.com
    traceroute to google.com (142.250.184.142), 30 hops max, 60 byte packets
     1  _gateway (192.168.1.1)  1.120 ms  1.013 ms  0.912 ms
     2  10.0.0.1 (10.0.0.1)  2.540 ms  2.487 ms  2.409 ms
     3  * * *
     4  * * *
     5  108.170.249.225 (108.170.249.225)  8.556 ms  8.581 ms  8.613 ms
     6  142.250.236.183 (142.250.236.183)  8.388 ms  8.351 ms  8.321 ms
     7  142.250.236.163 (142.250.236.163)  8.449 ms  8.412 ms  8.403 ms
     8  142.250.184.142 (142.250.184.142)  8.364 ms  8.354 ms  8.342 ms

  • Pathping to Google (Windows):

    Terminal window
    pathping google.com

  • Nmap Port Scan (Example: Check if HTTP port 80 is open):

    Terminal window
    nmap -p 80 google.com
    Starting Nmap 7.92 ( https://nmap.org ) at 2023-10-27 14:30 UTC
    Nmap scan report for google.com (142.250.184.142)
    Host is up (0.0072s latency).
    

    PORT   STATE SERVICE
    80/tcp open  http
    

    Nmap done: 1 IP address (1 host up) scanned in 0.18 seconds

  • Netcat Port Check (Example: Check if HTTP port 80 is open):

    Terminal window
    nc -zv google.com 80
    Connection to google.com port 80 [tcp/http] succeeded!

  • DNS Lookup using dig:

    Terminal window
    dig google.com
    ; <<>> DiG 9.18.18 <<>> google.com
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33602
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
    

    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 512
    ;; QUESTION SECTION:
    ;google.com.                    IN      A
    

    ;; ANSWER SECTION:
    google.com.             299     IN      A       142.250.185.142
    

    ;; Query time: 0 msec
    ;; SERVER: 192.168.1.1#53(192.168.1.1)
    ;; WHEN: Fri Oct 27 14:31:22 UTC 2023
    ;; MSG SIZE  rcvd: 55

  • DNS Lookup using nslookup:

    Terminal window
    nslookup google.com
    Server:    192.168.1.1
    Address:  192.168.1.1#53
    

    Non-authoritative answer:
    Name:  google.com
    Address: 142.250.184.142

  • Telnet Port Check (Avoid in production, example only):

    Terminal window
    telnet google.com 80

    (If successful, a blank screen will appear, indicating a connection. Type Ctrl+] and then quit to exit.)

  • Test-NetConnection (PowerShell):

    Terminal window
    Test-NetConnection google.com -Port 443
    ComputerName           : google.com
    RemoteAddress          : 142.250.184.142
    RemotePort             : 443
    InterfaceAlias         : Wi-Fi
    SourceAddress          : 192.168.1.10
    TcpTestSucceeded       : True

4. Common Options

  • Ping:
    • -c <count> (Linux/macOS): Number of ping packets to send.
    • -n <count> (Windows): Number of ping packets to send.
    • -i <interval> (Linux/macOS): Interval between ping packets (seconds).
    • -w <timeout> (Linux/macOS): Timeout in seconds.
    • -t (Windows): Ping continuously until stopped.
    • -s <size>: Packet size (bytes).
    • -I <interface>: Source interface or address (Linux/macOS).
    • -f: Flood ping (Linux/macOS) (Use with caution!).
  • Traceroute/Tracert:
    • -m <max_hops>: Maximum number of hops.
    • -w <timeout>: Timeout for each hop.
    • -I (Linux/macOS): Use ICMP instead of UDP.
    • -d (Linux): Enable socket-level debugging.
  • Pathping:
    • -h <max_hops>: Maximum number of hops to search for the destination.
    • -g <hostlist>: Loose source route along host list.
    • -p <period>: Period between pings (milliseconds).
  • Nmap:
    • -p <port(s)>: Specify port(s) to scan.
    • -sT: TCP connect scan (requires root on some systems).
    • -sU: UDP scan.
    • -sS: SYN scan (requires root).
    • -O: Enable OS detection.
    • -v: Verbose output.
    • -A: Aggressive scan (enable OS detection, version detection, script scanning, and traceroute).
  • Netcat:
    • -z: Zero-I/O mode (scan for listening daemons).
    • -v: Verbose output.
    • -l: Listen mode (for creating a simple server).
    • -p <port>: Specify source port.
    • -n: Numeric-only IP addresses, no DNS lookup.
    • -w <timeout>: Connection timeout in seconds.
  • dig:
    • +trace: Enable tracing of the DNS resolution path.
    • +short: Provide a concise answer.
    • @<server>: Specify the DNS server to query.
    • <query_type>: Specify the DNS record type (e.g., A, MX, CNAME, TXT).
  • nslookup:
    • server <server>: Change the default DNS server.
    • set type=<record_type>: Set the type of DNS record to query (e.g., A, MX).
  • Test-NetConnection (PowerShell):
    • -Port <port>: The port to test.
    • -InformationLevel Detailed: Provides more details about the connection.
    • -TraceRoute: Displays the route to the remote host.

5. Advanced Usage

  • Ping with custom packet size:

    Terminal window
    # Linux/macOS
    ping -s 1024 google.com
    

    # Windows
    ping -l 1024 google.com

    (Useful for testing MTU issues)

  • Traceroute with specific source interface:

    Terminal window
    # Linux/macOS
    traceroute -I -s 192.168.1.10 google.com

  • Nmap comprehensive scan:

    Terminal window
    nmap -A -p 1-65535 -T4 google.com

    (Scans all ports, performs OS detection, version detection, and script scanning. -T4 is an aggressive timing template. Use with caution on production networks.)

  • Netcat file transfer:

    Terminal window
    # Server (listening)
    nc -l -p 1234 > received_file.txt
    

    # Client (sending)
    nc <server_ip> 1234 < file_to_send.txt

  • Dig to trace the DNS resolution path:

    Terminal window
    dig +trace google.com

  • Using dig to query a specific DNS server:

    Terminal window
    dig @8.8.8.8 google.com

  • Combining tools for deeper analysis: If ping is failing, use traceroute to identify where the connection is breaking down. Use nmap to check if necessary ports are open on the destination.

6. Troubleshooting Scenarios

  • No connectivity (Ping fails):
    • Possible Causes: Network cable disconnected, incorrect IP address, firewall blocking ICMP, router down, DNS resolution failure.
    • Troubleshooting Steps:
      1. Verify physical connection.
      2. Check IP address configuration.
      3. Temporarily disable firewalls to test.
      4. Ping the gateway.
      5. Ping an external IP address directly (e.g., 8.8.8.8). If that works, DNS is likely the issue.
      6. Use traceroute to identify where the path is failing.
  • High latency (Slow Ping times):
    • Possible Causes: Network congestion, high CPU load on network devices, routing issues, distance to destination.
    • Troubleshooting Steps:
      1. Use traceroute to identify hops with high latency.
      2. Check network device utilization (CPU, memory, interface bandwidth).
      3. Run pathping (Windows) for packet loss statistics at each hop.
      4. Test network speed using iperf3 or similar tools.
  • Packet loss (Ping shows dropped packets):
    • Possible Causes: Network congestion, faulty network hardware, MTU issues, firewall dropping packets.
    • Troubleshooting Steps:
      1. Check network device utilization.
      2. Test with different packet sizes to identify MTU issues.
      3. Examine firewall logs.
      4. Check for hardware errors on network interfaces.
  • DNS resolution failure (Ping by hostname fails, but by IP works):
    • Possible Causes: Incorrect DNS server configuration, DNS server unavailable, DNS record missing.
    • Troubleshooting Steps:
      1. Verify DNS server configuration.
      2. Use dig or nslookup to query the DNS server directly.
      3. Flush the DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on macOS).
  • Port connectivity issues (e.g., cannot connect to a web server):
    • Possible Causes: Firewall blocking the port, service not running on the destination, incorrect port number.
    • Troubleshooting Steps:
      1. Use nmap or nc to check if the port is open on the destination.
      2. Verify that the service is running and listening on the correct port.
      3. Check firewall rules on both the source and destination.
      4. Use Test-NetConnection -Port <port> in PowerShell.

7. Output Interpretation

  • Ping:
    • time: Round-trip time (RTT) in milliseconds. Lower is better.
    • ttl: Time-to-live. Indicates the number of hops the packet can traverse before being discarded.
    • packet loss: Percentage of packets that were not received. 0% is ideal.
  • Traceroute/Tracert:
    • Each line represents a hop along the path.
    • Asterisks (*) indicate a timeout. Multiple asterisks in a row suggest a network issue.
    • The IP address and hostname (if available) of each router are displayed.
    • The RTT for each hop is shown in milliseconds.
  • Pathping:
    • Provides similar hop information to traceroute.
    • Includes “This Node/Link Lost” statistics, showing packet loss at each hop.
  • Nmap:
    • Shows the state of each scanned port (open, closed, filtered).
    • Provides service and version information if available.
  • Netcat:
    • “Connection refused” indicates that no service is listening on the specified port.
    • “Connection timed out” indicates a network issue or firewall blocking the connection.
  • dig/nslookup:
    • ANSWER SECTION: Contains the DNS records that were returned for the query.
    • status: NOERROR: Indicates that the DNS query was successful.
    • SERVER: Shows the DNS server that was used to resolve the query.
  • Test-NetConnection (PowerShell):
    • TcpTestSucceeded: True indicates TCP connection to the port was successful.
    • PingSucceeded: True indicates ICMP ping to the host was successful.
    • TraceRoute: Displays the route to the remote host.

8. Security Considerations

  • Ping:
    • ICMP can be disabled by firewalls, making ping unreliable for connectivity testing in some environments.
    • Large ping floods (ping -f) can be used for denial-of-service attacks. Avoid using them on production networks.
  • Traceroute/Tracert:
    • Reveals network topology, which could be used by attackers to map the network.
  • Nmap:
    • Considered a security scanning tool. Scanning networks without permission is illegal in many jurisdictions.
    • Aggressive scans can trigger intrusion detection systems (IDS) and intrusion prevention systems (IPS).
    • Do not run Nmap scans from publicly accessible servers.
  • Netcat:
    • Can be used to create backdoors or transfer malicious files. Restrict access to Netcat on production systems.
    • Avoid using Netcat for transmitting sensitive data without encryption.
  • Telnet:
    • Transmits data in clear text, making it highly vulnerable to eavesdropping. Avoid using Telnet in production environments. Use SSH instead.
  • General:
    • Always use strong passwords and authentication mechanisms on network devices.
    • Implement network segmentation to limit the impact of security breaches.
    • Regularly review firewall rules and security policies.

9. Platform Differences

  • Ping: Basic functionality is similar across platforms. Options may vary slightly (e.g., -c vs. -n for packet count).
  • Traceroute/Tracert: traceroute is used on Linux/macOS, tracert on Windows. The output format differs slightly.
  • Pathping: Windows-specific tool.
  • Nmap: Available for Linux, Windows, and macOS. The command-line options are generally consistent across platforms.
  • Netcat: Different implementations exist (e.g., GNU Netcat, Ncat). Options may vary slightly. Ensure you are using a trusted version. BusyBox includes a minimal netcat implementation.
  • dig: Typically available on Linux and macOS. Windows may require installing a separate package (e.g., BIND).
  • nslookup: Available on all platforms, but often considered deprecated in favor of dig.
  • Telnet: Available on most platforms, but discouraged for security reasons.
  • Test-NetConnection: PowerShell cmdlet, Windows only.

This cheat sheet provides a comprehensive overview of ping and connectivity testing tools. Remember to practice these commands in a safe environment before using them on production networks. Always prioritize security and avoid actions that could disrupt network services.