Situatie
Network troubleshooting becomes much easier when you stop treating “the internet doesn’t work” as one problem. Connectivity depends on multiple layers.
1. No IP Address
Run:
ipconfig /all
If the adapter does not have the expected configuration, investigate DHCP or static IP settings. An address in the 169.254.x.x range often indicates that Windows automatically assigned an APIPA address because normal address configuration was unavailable.
2. No Default Gateway
Without an appropriate route, the PC may communicate locally but fail to reach external networks. Check the default gateway in ipconfig /all.
3. DNS Failure
Test an IP address and a hostname separately.
For example:
ping 1.1.1.1
followed by:
nslookup example.com
If IP connectivity works but name resolution fails, investigate DNS.
4. Wi-Fi Connected but No Internet
“Connected” only means the computer has established a wireless connection to the access point. It does not prove the router itself has internet connectivity. Check other devices and the router’s WAN status.
5. Disabled Network Adapter
Check:
Settings → Network & internet → Advanced network settings
or use:
Get-NetAdapter
to inspect adapter state.
6. Duplicate IP Addresses
Static addressing can cause conflicts when two devices are assigned the same address. Review DHCP reservations and manually configured addresses.
7. Incorrect Proxy
An unwanted proxy configuration can break browsers and applications even while basic network connectivity remains functional. Review proxy settings if only particular applications fail.
8. VPN Problems
VPN clients modify routing and sometimes DNS behavior. Disconnect the VPN temporarily during diagnosis if organizational policy permits it.
9. Driver Problems
If a network issue began after an update or hardware change, inspect Device Manager and the adapter driver. Do not automatically install random third-party “driver updater” utilities.
10. The Network Stack needs deeper investigation
Useful Windows commands include:
ipconfig /all
route print
arp -a
nslookup
tracert
and PowerShell’s:
Test-NetConnection
The important part is knowing what each test proves.
Leave A Comment?