Network, DNS & VPN troubleshooting
Wi-Fi/Ethernet, DHCP/IP, DNS, adapters, proxy/VPN and connection failures.
Classify the failing layer first: adapter/link, DHCP/IP, gateway, DNS, proxy/VPN, browser transport or upstream network.
Move to Winsock/TCP-IP/Network reset only after the narrower layer is identified and simpler diagnostics fail.
Is Wi-Fi/Ethernet present, enabled and physically connected?
Did Windows receive a usable address, gateway and lease?
Can the PC reach beyond its local adapter/network?
Do hostnames resolve through the configured DNS path?
Is traffic being rerouted, filtered or changed by policy/tunnel state?
Does the failure follow one browser/app or the whole Windows network?
Wi-Fi not working in Windows 11: a safe troubleshooting order
Diagnose a Windows 11 Wi-Fi problem from the least disruptive checks to network reset.
Ethernet not working in Windows 11: isolate cable, router, adapter and Windows
Separate a physical Ethernet path failure from a PC-only network-stack or driver problem before using network reset.
169.254 IP address in Windows 11: diagnose DHCP before resetting the network
A 169.254.x.x IPv4 address is a strong clue that Windows did not receive a usable DHCP address from the router or DHCP server.
DNS not resolving in Windows 11: prove name resolution before changing DNS settings
Use IP configuration, nslookup and a browser comparison to separate DNS failure from general connectivity or one-site failure.
Connected but no Internet in Windows 11: identify IP, DNS or upstream failure
A connected Wi-Fi/Ethernet icon does not prove usable Internet; check addressing, gateway, DNS and another device before resetting Windows.
Proxy blocking Internet in Windows 11: verify whether the proxy is intentional first
A manual proxy or setup script can be required by work/school networks, so distinguish stale configuration from managed policy before disabling it.
VPN connected but no Internet in Windows 11: separate tunnel policy from Windows networking
Compare the connection with and without the VPN, preserve organization policy, and avoid network reset until the failure is proven to be Windows-wide.
Commands used in this system
IPCONFIG FlushDNS
ipconfig /flushdnsClear the DNS client resolver cache on Windows.
Low riskIPCONFIG Release / Renew
ipconfig /release
ipconfig /renewRelease the current DHCP lease and request a new IP configuration from the network.
Medium riskNETSH Winsock Reset
netsh winsock resetReset the Winsock catalog used by Windows networking applications.
Medium riskNETSH TCP/IP Reset
netsh int ip resetReset TCP/IP configuration state as part of deeper Windows network repair.
Low riskIPCONFIG /all
ipconfig /allDisplay full TCP/IP configuration for all adapters, including addressing information useful for DHCP, gateway and DNS diagnosis.
Low riskNSLOOKUP
nslookup example.comQuery DNS name-resolution information so a hostname failure can be distinguished from general IP connectivity problems.
Low riskPING
ping <targetname>Test IP-level reachability and round-trip responses to a TCP/IP host; comparing a hostname with an IP can also provide name-resolution clues.
Low riskTRACERT
tracert <targetname>Trace the IP path toward a destination using increasing TTL values, providing hop/latency clues without changing network settings.