"The internet isn't working" can mean a dozen different things. Instead of trying random fixes, test the connection layer by layer, starting with the computer and moving outwards. Each step either finds the problem or rules out a whole category of causes.

All commands work in an ordinary (non-admin) terminal unless stated otherwise.

Check the network adapter

Is the computer connected at all? In PowerShell:

PowerShell
Get-NetAdapter | Select-Object Name, Status, LinkSpeed

You want your Ethernet or Wi-Fi adapter to show Up. If it shows Disconnected, check the cable, Wi-Fi connection, or whether the adapter is disabled.

Check the IP configuration

CMD
ipconfig /all

Look at the active adapter and check four things:

  • IPv4 Address — should be in your network's range, such as 192.168.1.25.
  • Default Gateway — usually your router, such as 192.168.1.1.
  • DNS Servers — must be present.
  • DHCP Enabled — usually Yes on home and office networks.

An address starting with 169.254 means the computer could not contact a DHCP server. Try renewing the address (Step 3).

Renew the IP address

CMD
ipconfig /release
ipconfig /renew

If renewal fails, the problem is between the computer and the DHCP server — often the router, a switch port or the Wi-Fi network itself.

Ping the default gateway

CMD
ping 192.168.1.1

Replace the address with your own default gateway. Replies mean your local network is working. If this fails, the problem is local: cable, Wi-Fi signal, switch or router.

Ping a public IP address

CMD
ping 1.1.1.1

This tests whether traffic leaves your network, without using DNS. If the gateway replies but this does not, the problem is the router's internet connection or the internet provider.

Test DNS name resolution

PowerShell
Resolve-DnsName example.com

If you could ping 1.1.1.1 in Step 5 but this fails, DNS is the problem. Clear the cache with ipconfig /flushdns and check the DNS servers you saw in Step 2. See How DNS Works for more detail.

Test the specific service

Sometimes the network is fine but one service is blocked. Test-NetConnection checks whether a TCP port is reachable:

PowerShell
Test-NetConnection example.com -Port 443

TcpTestSucceeded : True means the server is reachable on that port. False points to a firewall, proxy or a problem with the server itself.

Reading the results

Last step that workedMost likely cause
None — adapter is downCable, Wi-Fi, disabled adapter or driver
Adapter is up, but IP is 169.254.x.xDHCP server or router not reachable
IP is valid, but gateway does not replyLocal network: Wi-Fi, switch, router
Gateway replies, public IP does notRouter's internet connection or provider
Public IP replies, names do not resolveDNS settings or DNS server
Names resolve, but one site or app failsFirewall, proxy, VPN or the remote service

Tracing the route

To see where along the path packets stop, use tracert or its PowerShell equivalent:

PowerShell
Test-NetConnection example.com -TraceRoute

Some routers do not reply to trace requests, so a few * entries in the middle of a trace are normal. Only consistent failures from a certain point onward are meaningful.

Last resort: reset the network stack

If settings are corrupted — often after VPN software has been removed — reset Windows networking. Run these in an administrator terminal, then restart:

CMD
netsh winsock reset
netsh int ip reset

On Windows 11 you can achieve the same from Settings → Network & internet → Advanced network settings → Network reset.