Networking interview question · Most asked
A service is unreachable. How do you troubleshoot it systematically?
Summary
Work up the layers from the client: does DNS resolve to the expected address; is there a route; does a TCP connection open (timeout suggests filtering, 'connection refused' suggests nothing listening); does TLS validate; what does HTTP return; is the app listening on the right address? Then use flow logs and reachability tools to find the blocking rule.
Longer Answer
Commands: dig, ip route get, nc -vz host port, openssl s_client, curl -v, ss -tlnp, tcpdump. Cloud: VPC Flow Logs, Reachability Analyzer, Azure Network Watcher, Google Cloud Connectivity Tests. Don't rely on ping; ICMP is often blocked.
Key Points
- DNS -> route -> TCP -> TLS -> HTTP -> app.
- Timeout vs refused tells you a lot.
- Flow logs show accepts and rejects.
- Ping alone proves nothing.
Deep dive: Networking Tutorial: Network Troubleshooting
Explanation
What interviewers look for
A methodical approach and interpretation of symptoms.
More most-asked Networking questions
- How does NAT work, and what are its limits?
- What's the difference between TCP and UDP, and when would you choose UDP?
- What do 502, 503 and 504 errors from a load balancer usually mean?
- What is CIDR notation? How many usable addresses are in a /26, and in an AWS /26 subnet?
- How does DNS resolution work, and what does a record's TTL control?
- What does TLS provide, and how does certificate validation work?
- What happens, at the network level, when you type a URL into a browser and press Enter?
- What's the difference between stateful and stateless firewalls? Give cloud examples.