Windows network troubleshooting cheat sheet
Inspect addressing, DNS resolution and TCP reachability with PowerShell.
Windows 10/11 and Windows Server with NetTCPIP and DnsClient modules.
Updated · Windows · 7 min read
| Command | What it does |
|---|---|
Get-NetIPConfiguration | Inspect addresses and gateways |
Get-NetAdapter | Inspect adapter state and link speed |
Resolve-DnsName server.example.com | Resolve a host name |
Test-NetConnection server.example.com -Port 443 | Test a specific TCP service |
Walkthrough
Open PowerShell on the affected host. Replace server.example.com with an approved test host; TCP tests send probes.
Step 1: Inspect addresses and gateways
Get-NetIPConfiguration
Find the adapter carrying the affected traffic. Compare its address, default gateway and DNS servers with the intended subnet. Disconnected adapters may appear alongside the active one.
Step 2: Inspect adapter state and link speed
Get-NetAdapter
Match the interface name to the physical or virtual adapter. A disconnected interface points to a link or virtual-switch issue before DNS becomes relevant.
Step 3: Resolve a host name
Resolve-DnsName server.example.com
Replace the example name with your target. Check the answer and record whether the response is NXDOMAIN, a timeout or an unexpected address; these indicate different failure paths.
Step 4: Test a specific TCP service
Test-NetConnection server.example.com -Port 443
Check TcpTestSucceeded and the selected source address. A successful test confirms a TCP connection, not application authentication or TLS correctness.