How to read this page
Windows still ships a large set of CMD-era tools (ipconfig, ping, netstat, nslookup, route) plus netsh modules. Modern builds also expose richer, scriptable views through PowerShell networking cmdlets. Use CMD tools for muscle memory and quick copy-paste; use PowerShell when you need objects, filtering, and automation.
Core CMD commands
| Command | Typical use | Notes |
|---|---|---|
ipconfig /all | DHCP lease, gateways, DNS servers per adapter | Pair with /release /renew only when you understand impact |
ipconfig /flushdns | Clear the client DNS cache | Does not flush upstream resolver or browser DoH |
ping / tracert | ICMP reachability and hop path | Blocked ICMP does not imply TCP failure |
pathping | Loss per hop over time | Slower than tracert; better for flaky links |
netstat -ano | Listening ports and TCP connections with PIDs | Use Task Manager or tasklist /fi to map PID to image |
nslookup | Query DNS against a chosen server | Non-interactive mode avoids stuck interactive shell |
route print | IPv4/IPv6 route tables and metrics | VPN split tunneling shows up as interface-specific routes |
arp -a | IPv4 neighbor cache on the LAN segment | Less central on routed IPv4; neighbor discovery differs on IPv6 |
getmac | Adapter MAC addresses | Useful for DHCP reservations and 802.1X |
netsh … | WLAN profiles, winhttp proxy, trace, firewall (legacy surface) | Many areas now have PowerShell-first equivalents—check docs per subsystem |
PowerShell you will reuse
Get-NetIPAddress and Get-NetIPConfiguration replace much of ipconfig for scripting. Get-NetRoute aligns with route print. Get-NetTCPConnection parallels netstat with filterable objects. Test-NetConnection combines reachability probes with optional TCP tests. Resolve-DnsName is the structured alternative to nslookup; Clear-DnsClientCache matches ipconfig /flushdns.
Elevation and scope
Reading state is often possible without Administrator; changing routes, proxies, WLAN profiles, or firewall rules usually is not. When Hyper-V, Docker, or VPN clients install virtual adapters, always label which interface you tested—metrics and binding order change outcomes.
Deeper dives: ipconfig, ping, tracert, netstat, PowerShell networking, Linux vs Windows commands.