Networking Troubleshooting

Windows 11 Troubleshooting & Administration

Chapter 8 · Networking Troubleshooting

Networking Fundamentals 10 already built a real diagnostic workflow around ping, traceroute, ss, and tcpdump. Windows 11 Fundamentals 7 previewed ipconfig /flushdns without using it. This chapter delivers the Windows-specific tools and applies that same layered workflow directly.

ipconfig — Adapter State & DNS Cache

ipconfig /all shows every adapter's full configuration — IP address, subnet mask, default gateway, and DNS servers, whether assigned by DHCP or set manually. ipconfig /release followed by ipconfig /renew forces a fresh DHCP lease, useful when an adapter is stuck with an invalid or conflicting address. ipconfig /flushdns finally delivers on Windows 11 Fundamentals 7's own preview — clearing the local DNS resolver cache, useful when a domain name has recently changed its IP address but Windows keeps resolving the stale one.

ping — Basic Reachability, Read Correctly

ping -t pings continuously until stopped; ping -n <count> sends a specific number of requests. Two very different failure messages are worth distinguishing precisely:

Message	What it actually means
Request timed out	No response came back at all within the wait period — could be a dropped packet, a firewall silently discarding it, or genuine unreachability
Destination host unreachable	A router along the way actively knows there's no valid path to that destination and said so — a routing-level "no," not silence

tracert — The Windows-Specific Hop-by-Hop Path

tracert shows every router hop between this machine and a destination, revealing exactly where a connection breaks down along the route. One genuine technical difference from Networking Fundamentals 10's own traceroute coverage: Windows's tracert uses ICMP Echo requests by default, while several Unix/Linux traceroute implementations default to UDP — the same underlying concept, a different default protocol, occasionally producing different results against a firewall that filters one but not the other.

nslookup — Isolating DNS Specifically

nslookup <domain> queries DNS directly and shows exactly what it resolves to. Pointing it explicitly at a known-good public DNS server (nslookup example.com 8.8.8.8) isolates whether a resolution failure is specific to the machine's own configured DNS server, or a broader problem affecting DNS resolution generally.

A Real Layered Troubleshooting Workflow

The Windows-tool version of Networking Fundamentals 10's own methodology

ipconfig /all — does this machine have a valid IP address and gateway at all?
ping the default gateway — can this machine reach the local network?
ping 8.8.8.8 (a known IP, bypassing DNS entirely) — can this machine reach the internet at all?
nslookup a domain — is DNS resolution itself working?
ping the domain name directly — does it resolve and respond together?

Each step isolates one specific layer, exactly matching Networking Fundamentals 10's own layered diagnostic philosophy — just expressed through Windows's own specific tools rather than their Linux counterparts.

Pinging a raw IP to separate connectivity from DNS

Step 3 above is worth calling out on its own: pinging 8.8.8.8 directly, with no domain name involved, proves or disproves general internet connectivity completely independently of whether DNS is working — a fast, genuinely useful way to narrow "the internet doesn't work" down to either a connectivity problem or a DNS-specific one in a single command.

Network Reset — A Genuine Last Resort

Settings > Network & internet > Advanced network settings > Network reset reinstalls every network adapter and resets networking components to their default state.

Network Reset is disruptive, not a quick first step

Network Reset removes VPN configurations and resets adapter-specific settings entirely — a genuinely bigger action than anything else in this chapter, appropriate only once the layered workflow above has already been worked through and hasn't isolated the problem. Reaching for it first, before ipconfig/ping/nslookup have even been tried, risks losing working configuration to fix a problem that a five-minute layered check might have identified precisely.

Hands-On Exercises

Exercise 1

A ping to a website returns "Destination host unreachable" while a ping to a different site returns "Request timed out." Using this chapter's own compare-table, explain the different underlying meaning of each result.

📄 View solution

Exercise 2

A user reports "the internet is down." Using this chapter's own five-step workflow, explain what pinging 8.8.8.8 directly (rather than a domain name) actually isolates, and why that step matters before checking DNS.

📄 View solution

Exercise 3

A colleague suggests running Network Reset as the very first troubleshooting step for a Wi-Fi connectivity issue. Using this chapter's own warn-box, explain why that's premature.

📄 View solution

Chapter 8 Quick Reference

ipconfig /all, /release, /renew, /flushdns — adapter state and DNS cache, delivering on Windows 11 Fundamentals 7's own preview
"Request timed out" (no response) vs. "Destination host unreachable" (an active routing-level no) are genuinely different findings
tracert uses ICMP by default — a real difference from some Linux traceroute implementations' own UDP default
Pinging a known IP directly isolates general connectivity from DNS-specific problems
A five-step layered workflow (gateway → known IP → nslookup → domain ping) mirrors Networking Fundamentals 10's own methodology using Windows tools
Network Reset is genuinely disruptive — a last resort, not a first step
Next chapter: Boot & Startup Issues