Network Troubleshooting Methodology
A repeatable, evidence-led approach to isolating network faults by layer.
Start with the Symptom, Not a Favorite Command
A staff member says, “The app is down.” That statement is a symptom, not a diagnosis. Ask what is failing, for whom, since when, from which network, and whether the failure is complete or intermittent. A useful problem statement is: “Users on the office Wi-Fi cannot resolve the payroll hostname; wired users can; the issue began after a DNS configuration change at 09:20.”
Build a simple path model: client, local link, gateway, DNS resolver, route, firewall, load balancer, service, and dependencies. Identify the last known-good hop and the first failing one. Record timestamps and exact errors before changing configuration. One change at a time makes cause and effect easier to understand.
Use a Layered, Evidence-Led Sequence
Physical/link: check Wi-Fi association, cable, interface state, speed/duplex, VLAN, and local error counters. Network: inspect address, prefix, gateway, route, and reachability. Name resolution: query the intended resolver and compare with a known-good name. Transport: test whether the expected port is reachable. Application: inspect TLS, HTTP status, server logs, and dependencies.
A successful ping does not prove that a web service works: ICMP may be blocked, or the server may answer ICMP while its application is unhealthy. A failed ping does not prove the host is offline. Use the test that matches the suspected layer, and distinguish “not tested” from “failed.”
# Read-only local checks (Linux examples)
ip -brief address
ip route
ip route get 10.20.4.15
# DNS: ask the intended resolver explicitly
getent hosts app.internal.example
# Test an application port you are authorised to access
curl -I --connect-timeout 3 https://app.example.test/healthA Worked Case: Name Resolves, Connection Times Out
Suppose a client can resolve inventory.internal to 10.20.4.15, but its HTTPS request times out. DNS is less likely to be the immediate fault. Check the selected route, then whether the network path allows TCP/443, then whether the server is listening and healthy. If the route points at the expected VPN or gateway, compare from a second authorised client and review firewall logs for a matching timestamp and source/destination pair.
If the TCP connection establishes but TLS fails, the problem has moved up the stack: check certificate validity, server name, supported protocol configuration, and any inspection proxy. If TLS works and the response is HTTP 503, investigate the application or an upstream dependency rather than changing the client's default route.
# Decision record (fill with observed evidence)
DNS answer: 10.20.4.15 from resolver 10.20.0.53
Route: via wg0, source 10.8.0.24
TCP/443: timeout from client A; succeeds from client B
TLS: not reached on client A
Firewall log: pending lookup at 09:34Z
Current hypothesis: path or policy differs for client ATools and Their Limits
ping checks ICMP echo when allowed; traceroute or tracepath infers hops from TTL behaviour, but routers may suppress or rate-limit responses. dig and nslookup query DNS. ip shows Linux addresses and routes; ss inspects sockets. Browser developer tools expose request timing and HTTP details. Packet capture can answer questions about an observed exchange, but it may contain private data and needs a narrow filter and authorised scope.
Compare endpoints and time windows carefully. A test from a server room does not reproduce a home ISP path. A single traceroute is not a complete map because return paths may differ. Keep command output with timestamps and redact account names, cookies, tokens, and internal details before sharing it.
# Useful read-only checks
ss -lnt # local listening TCP sockets
ip neigh show # local neighbour cache
tracepath app.example.test
# Compare resolver answers with an approved resolver
dig app.example.test
dig @10.20.0.53 app.internal.exampleEscalate with a Useful Handoff
A high-quality escalation includes impact, scope, start time, recent changes, exact reproduction steps, evidence gathered, and the next unanswered question. “Network issue” gives the next team no starting point. “Only Wi-Fi clients in building A fail; wired clients succeed; DNS is correct; TCP/443 times out; no local route change is present” directs investigation toward wireless-to-server policy or path differences.
After restoration, identify the root cause and contributing conditions, not just the first alert. Add a monitoring signal or test that would have detected the issue earlier. Document the fix and remove temporary workarounds that could create a security or reliability problem.
Mistakes, Practice, and Review
Common mistakes: changing multiple settings simultaneously; treating ICMP as a complete health check; skipping timestamps; and assuming DNS is at fault whenever an application name is mentioned. Separate observations, hypotheses, and conclusions in your notes.
Practice: (1) Write a precise problem statement for “video meetings are choppy.” (2) Build a layer-by-layer test sequence for one client unable to open an internal dashboard. (3) Interpret the worked case and identify two next checks. (4) Draft a concise escalation note from your results. (5) List sensitive data to redact from a packet capture.
🎯 Key Takeaways
- ✓Define impact, scope, start time, and exact symptoms before testing.
- ✓Trace the path from local link through routing, DNS, transport, TLS, application, and dependencies.
- ✓Choose a test for the layer in question; ping and traceroute each have important limitations.
- ✓Change one thing at a time and record observations separately from hypotheses.
- ✓Use least-intrusive, authorised diagnostics and protect data collected during troubleshooting.
- ✓A useful handoff includes evidence, scope, recent changes, and the next question—not just “the network is down.”
HELP US IMPROVE
How was this lesson?
Your note is shared with the Chaduvuko team for review. Please don’t include personal or sensitive information.
Spotted a mistake or something unclear? Suggest a fix on GitHub or email us. Select the text first and it is quoted for you.
Discussion
0Have a better approach? Found something outdated? Share it — your knowledge helps everyone learning here.
