Windows Says Connected but No Internet? Check These 5 Things

Windows says it is connected, but websites will not load? Work outward: Link → IP → Gateway → Internet → DNS. In plain English, check the cable or Wi-Fi, Windows’ network settings, the local router, a remote IP, then a website name. Stop at the first failure. Before changing settings, test another device on the same connection.

Result	Where to look next
Another device fails on the same connection	Shared cable, switch, access point, router, or service
Address starts with 169.254	DHCP or the path to DHCP
Default gateway is blank	IP configuration or DHCP
Gateway replies, but a remote IP does not	Router, internet service, VPN, or upstream firewall
Remote IP replies, but a name does not resolve	DNS

First, check the scope

If another device works on the same cable, desk, or Wi-Fi network, focus on the original Windows device. If several devices fail in the same place, look for a shared problem.

Ask what changed recently. A desk move, update, VPN change, or network change can shorten the search.

1. Is the device actually connected?

For Ethernet, check the link light, reseat the cable, and bypass the dock if possible. A known-good cable can separate a device problem from the wired path.

For Wi-Fi, confirm the correct network name (SSID), check the signal, reconnect, and test another device on the same SSID when possible.

A link light or Wi-Fi status of “Connected” does not prove that the device received an address or can reach the internet. After an access point change, use the focused new access-point troubleshooting guide.

2. Did Windows receive usable IP settings?

Run this to inspect the active adapter:

ipconfig /all

Find the adapter in use, then check its IPv4 address, subnet mask, default gateway, and DNS servers. Ignore disconnected adapters so an old VPN or virtual adapter does not distract you.

An address beginning with 169.254 is an Automatic Private IP Addressing (APIPA) address. Windows assigned it because settings did not arrive from Dynamic Host Configuration Protocol (DHCP). Check the cable or Wi-Fi path and whether other devices can get an address; the APIPA note covers the deeper workflow.

A blank default gateway is also a stop sign because the device normally cannot leave its local network. Do not change DNS while either IP problem remains.

3. Can it reach the default gateway?

The default gateway is the router or firewall that carries traffic beyond the local network. Copy its address from ipconfig /all, then test it:

ping <default-gateway-address>

A reply means the local path is responding. Move to the remote-IP test. If it times out, stay local: compare another device and recheck the cable, SSID, adapter, dock, network port, or access point.

Some networks block ping, so treat a timeout as evidence to compare with other devices, not proof that the gateway is down.

4. Can it reach a remote IP address?

If policy permits, test an approved external IP address to check the path beyond the local network without using a website name:

ping 8.8.8.8

If it replies, the basic internet path works. Stop checking the cable and move to DNS.

If the gateway replies but the remote IP does not, compare another device. A one-device failure may involve a VPN, local firewall, or bad route. Several-device failures point to the router, internet service, or upstream network. Do not restart shared equipment without permission.

5. Does DNS resolve names?

Domain Name System (DNS) turns a name such as google.com into an IP address. Test it directly:

nslookup google.com

If ping 8.8.8.8 works but nslookup google.com times out or returns an error, DNS is the next suspect. Check the DNS server addresses shown by ipconfig /all, compare them with a working device, and note whether a VPN supplies different DNS settings.

If nslookup returns one or more addresses, DNS answered. A single website may be down, or the remaining issue may involve the browser, proxy, VPN, or firewall policy. The broader DHCP, DNS, and default-gateway note explains how those settings fit together.

Verify the fix or hand off useful evidence

After a change, repeat the failed check first, then open a known-good website. Do not call it fixed only because Windows still says “Connected.”

For escalation, record the affected devices or area, wired or Wi-Fi connection, active adapter, IP address, gateway, and the gateway, remote-IP, and DNS test results. This shows where the path stopped without a command dump.