Master Network Troubleshooting: A Complete Step‑by‑Step Guide

Network Troubleshooting Overview

Network troubleshooting is an essential skill for developers and IT professionals, enabling them to quickly diagnose why a computer cannot access the internet.

Note: A computer may have multiple network interfaces. PCI network card for wired connections. Wireless card for Wi‑Fi. Virtual NICs when virtual machines are installed.

Essential Prerequisites

Before diving into commands, you need a solid understanding of the OSI seven‑layer model, the TCP/IP stack, and the basic network devices and their corresponding layers.

1.1 Understand OSI Model and TCP/IP Stack

The OSI model and the DoD (TCP/IP) model describe how data moves through a network. Key protocols you must know include DNS, TCP, UDP, IP, ICMP, and ARP.

1.2 Network Devices and Their OSI Layers

Typical devices include switches (Layer 2), routers (Layer 3), firewalls, and three‑layer switches. Understanding which layer each device operates on helps pinpoint failures.

1.3 Basic Architecture of Small‑to‑Medium Enterprise Networks

Common layout: Access layer → Aggregation layer → Core layer → Internet edge.

1.4 Common Network Diagnostic Commands

Windows: ipconfig – view IP address, subnet mask, gateway. ipconfig /all – view DNS servers as well. ping – test connectivity. nslookup – query DNS. tracert -d – trace route without reverse DNS. arp -a – view MAC address of the gateway.

Linux commands are analogous (e.g., ifconfig, ping, traceroute, nslookup).

1.5 Key Principle: Follow the Data Flow

Always track the path data takes; this guides you to the faulty segment.

Basic Troubleshooting Process

Check physical link (cables, NIC, switch port).

Verify local IP, routing, and DNS settings.

Test gateway and router connectivity step by step.

Ping an external IP (e.g., 8.8.8.8) to confirm internet reachability.

Ping a website or use nslookup to validate DNS.

Detailed Steps with Example Topology

An example GNS3‑based network is used to illustrate each step.

3.1 Physical Link Check

Ensure the NIC is functional, the cable is intact, and the switch port is active. If possible, use a cable tester or a known‑good laptop.

Check NIC status.

Check cable condition.

Check switch port connection.

3.2 Verify IP, Routing, DNS Settings

Use ipconfig (Windows) or ifconfig (Linux) to view IP configuration. Ensure DHCP is enabled or static IP settings are correct, including subnet mask and default gateway.

3.3 Test Gateway and Router Connectivity

Ping the gateway (e.g., 192.168.2.254). If successful, ping the next router (e.g., 172.16.13.1). Use tracert -d to see each hop.

3.4 Ping External IP

Ping public IPs such as 8.8.8.8 or 114.114.114.114 to confirm internet connectivity without DNS interference.

3.5 Test DNS Resolution

Ping a domain name (e.g., www.google.com) and use nslookup to verify the DNS server returns the correct IP.

The overall process emphasizes a logical, data‑flow‑centric mindset, allowing you to isolate the faulty segment efficiently.