Windows Says Connected but No Internet: Complete Troubleshooting Guide

The fastest way to find the fault

Windows can show that a PC is connected to Wi-Fi or Ethernet without proving that it can reach the wider internet. The fault may be on the computer, cable or wireless link, router, modem, internet provider, or in DNS name resolution.

Use this sequence and stop when a test identifies a likely failing layer. It is faster and safer than resetting every network setting at once.

1. Scope: check whether other devices on the same network work, then test the PC on a phone hotspot.
2. Address: run ipconfig /all and inspect the IP address and default gateway.
3. Router: test whether the default gateway responds.
4. Internet: test a public IP address such as 1.1.1.1.
5. Names: test whether a website name resolves.
6. Software: check VPN, proxy, firewall, security software, and date/time.
7. Adapter and driver: investigate them next; use Network Reset only as a later step.

What “connected, no internet” actually means

Windows can show a connection when the adapter has joined a network and obtained an address from the router. Separately, Windows performs a small internet-connectivity check in the background. If that check fails, the network icon may show “No Internet” even while the link itself is working.

The warning can be wrong in either direction. If the icon says no internet but your browser works, the background check may be blocked by a VPN, proxy, firewall, DNS filter, or captive portal. If nothing loads, test the route from the PC to the router and then to the wider internet.

The layer ladder: what each test proves

Use this table as a map. A passing test narrows the search; a failing test points to the layer to inspect next.

Step 1: confirm the scope

1. Check another phone or computer on the same Wi-Fi or Ethernet network. If it is also offline, start with the router, modem, and provider rather than Windows.
2. Turn on a phone hotspot and connect the PC. If the PC works there, the computer is probably capable of connecting and the original network needs attention.
3. If you use Wi-Fi, test Ethernet if available; if you use Ethernet, test Wi-Fi. A difference helps isolate the adapter, driver, cable, or wireless signal.
4. Confirm Airplane mode is off and Wi-Fi is enabled.
5. On public or hotel Wi-Fi, open a plain http:// page to trigger a captive-portal sign-in page. Some networks show connected until you accept their terms.

Step 2: check the IP configuration

Open Windows Terminal or Command Prompt and inspect the active Wi-Fi or Ethernet adapter. You need to see a usable address, the router’s default gateway, a DHCP server where applicable, and at least one DNS server.

ipconfig /all

• IPv4 Address: normally a private address such as 192.168.x.x, 10.x.x.x, or 172.16.x.x through 172.31.x.x.
• Default Gateway: the router’s address; it should not be blank.
• DHCP Server: usually the router or another DHCP server on the network.
• DNS Servers: at least one DNS server should be listed.

Interpret the IP configuration

Compare the values in the active adapter with this table.

Release and renew the network address

For an adapter configured to obtain its address automatically, release the current DHCP lease and request a new one. The connection may drop briefly while this runs.

ipconfig /release
ipconfig /renew

If the address is still 169.254.x.x

Power off the router for about 30 seconds, turn it back on, wait for its lights to settle, and repeat the check. If another device also cannot obtain an address, the router’s DHCP service is a stronger suspect than the PC.

Step 3: test the gateway, a public IP, and a name

Run the following tests in order, replacing the gateway placeholder with the Default Gateway value shown by ipconfig. Note exactly which test first fails.

ping <your default gateway>
ping 1.1.1.1
ping example.com

What the ping results suggest

Use the first failing result to choose the next diagnostic step.

If ping results are inconclusive

Some networks block ping replies, so a failed ping alone is not conclusive. In PowerShell, test whether a real TCP connection to HTTPS port 443 opens. TcpTestSucceeded : True means the connection opened.

Test-NetConnection 1.1.1.1 -Port 443
Test-NetConnection example.com -Port 443

If names fail but the IP works: check DNS

Run a normal lookup, compare it with a lookup sent directly to a public resolver, and clear the local DNS cache. In PowerShell or Command Prompt, use the commands below.

If the direct lookup to 1.1.1.1 works but the normal lookup fails, the currently configured DNS server may be the problem. A successful direct lookup is a clue; compare multiple sites and devices before deciding the resolver is definitively at fault.

nslookup example.com
nslookup example.com 1.1.1.1
ipconfig /flushdns

Change DNS or trace the route

You can test a trusted resolver such as 1.1.1.1 and 1.0.0.1, 8.8.8.8 and 8.8.4.4, or 9.9.9.9 under Settings → Network & internet → your connection → DNS server assignment. Retest, and return to automatic DNS if the change does not help. You can also change DNS on the router so the setting applies to multiple devices.

To see where the route may be stopping, run tracert 1.1.1.1. The first hop is normally the router. Timeouts can occur when a router or provider filters trace traffic, so use the result with the other tests rather than treating a timeout as proof by itself.

tracert 1.1.1.1

Step 4: rule out VPN, proxy, and security software

These can block browsing while the network adapter itself looks healthy. Change one item at a time and retest.

1. Disconnect the VPN and close its app. Some clients leave a virtual adapter or kill-switch rule behind after a crash. Reconnect once and disconnect cleanly, or restart Windows.
2. Open Settings → Network & internet → Proxy. Turn off Use a proxy server unless it is intentionally configured. To inspect the system-wide WinHTTP proxy, run netsh winhttp show proxy. To clear it, run netsh winhttp reset proxy in an elevated Command Prompt only if you know a custom proxy is not required.
3. Check date and time. An incorrect clock can break secure HTTPS connections; enable automatic time and retest.
4. Temporarily pause third-party security filtering only as a controlled test. If browsing returns, update or reconfigure the product and turn protection back on immediately.
5. Inspect C:\Windows\System32\drivers\etc\hosts for unexpected entries affecting common websites. Do not delete entries unless you understand why they are present.
6. Try another browser. If only one browser fails, investigate its extensions and settings before changing Windows networking.

Step 5: check the router and modem

If several devices are offline—or the PC works on a hotspot but not on the original network—check the network side.

1. Check the modem or router status lights. Labels vary and may include Online, Internet, WAN, DSL, or PON. An abnormal internet indicator may point to a line or provider fault; check the device manual for the meaning of its exact light pattern.
2. Restart in order: turn off both modem and router for about 30 seconds, power on the modem first, wait until it is fully online, then power on the router.
3. Check provider outage information using mobile data on a phone. A service outage requires provider action, not Windows changes.
4. If you recently added a second router, check for a router-mode or double-NAT mix-up and confirm which device is providing DHCP.
5. Check whether the router has run out of DHCP addresses or has MAC filtering, parental controls, access schedules, or device-specific blocks enabled.
6. If DNS fails across devices, test a different DNS service on the router. Update router firmware when the manufacturer documents a relevant fix.
7. A router that needs frequent restarts may have a firmware problem or failing hardware; repeated rebooting is not a durable diagnosis.

Step 6: check the adapter and driver

If the PC is the only device affected, check its network adapter after the IP, gateway, DNS, and software tests.

1. Run the built-in troubleshooter from Settings → System → Troubleshoot → Other troubleshooters, including Network and Internet or Network Adapter when available. It can reset a stuck setting, but it is not a guaranteed fix.
2. Disable and re-enable the adapter under Settings → Network & internet → Advanced network settings.
3. In Device Manager → Network adapters → your adapter → Properties → Driver, review the driver history. If the problem began after a driver or Windows update, consider Roll Back Driver or install the correct driver from the PC or adapter manufacturer. Avoid third-party driver-download sites.
4. If available, open the adapter Properties → Power Management tab and untick Allow the computer to turn off this device to save power. This can help with Wi-Fi that connects and then drops.
5. For Wi-Fi, move closer to the router and compare 2.4 GHz with 5 GHz when your router supports both. Weak signal or band-specific trouble can look like a connected link with little useful traffic.
6. Use Restart rather than relying only on Shut down. With Fast Startup enabled, a shutdown may preserve part of the driver state; Restart reloads it.

Ethernet-specific checks

1. Swap the Ethernet cable and try another router or switch port. A damaged cable can still show a link.
2. Check the link and activity lights at the PC and router/switch ports, if present.
3. If a link expected to negotiate at gigabit speed shows only 100 Mbps or 10 Mbps, inspect the cable, connectors, and ports. The negotiated speed is a clue rather than proof of a particular fault.

Step 7: advanced checks for partial or unusual failures

Use these checks after basic connectivity, DNS, VPN/proxy, and adapter checks. They are useful for cases where some websites load while others hang or the issue persists despite a valid IP configuration.

MTU problems: some sites load, some hang

A mismatched packet size can break some connections. Test with the command below. If it reports that a packet needs fragmentation, lower the size—for example, to 1464 or 1452—until it works. Add 28 to the working payload size to estimate the MTU. This can matter behind some VPNs and tunnels; where possible, correct the router or tunnel MTU rather than applying a blind PC-side change.

ping example.com -f -l 1472

IPv6 versus IPv4

Compare the IPv4 and IPv6 results. If IPv4 works but IPv6 fails or browsing stalls, investigate the router’s IPv6 setting or ask the provider before disabling IPv6 on the PC as a workaround.

ping -4 example.com
ping -6 example.com

Event Viewer network errors

Open Windows Logs → System in Event Viewer and look for repeated network or DHCP Client errors near the time the connection failed.

When Network Reset is the right tool

Network Reset is a last software step, not the first one. It removes saved Wi-Fi networks, removes and reinstalls network adapters, and resets related settings. You may need to reconnect to Wi-Fi and reconfigure VPN or virtual network adapters afterward.

Consider it only after targeted checks fail and the evidence points to a damaged network stack—for example, other devices work, the adapter and driver appear healthy, and this PC cannot connect across multiple networks. Before resetting, record your Wi-Fi password, any static IP or custom DNS settings, and your VPN setup.

The built-in option is Settings → Network & internet → Advanced network settings → Network reset. These administrator commands perform narrower operations and are not all interchangeable with the Settings reset; restart Windows after a stack reset.

netsh winsock reset
netsh int ip reset
ipconfig /flushdns

Bench checks: separate hardware from Windows

If software fixes fail, test the hardware path before reinstalling Windows. Use a known-good network or adapter so that each test changes only one factor.

1. Try a USB Wi-Fi or Ethernet adapter. If it works immediately, the built-in adapter, driver, or antenna connection becomes a stronger suspect.
2. Boot from a Linux live USB or another operating system. If networking works there, Windows configuration or drivers become more likely; if it still fails, inspect the adapter, cable, and network path.
3. Test Ethernet using a known-good cable or cable tester and inspect damaged connectors.
4. On a laptop, inspect whether the Wi-Fi antenna cables are seated correctly on the wireless card. A loose or disconnected antenna lead can cause weak signal on one laptop in a room where other devices work.
5. Try the PC on a separate network, such as a hotspot or another router, to help establish whether the adapter can connect at all.

What not to do

• Do not reset the network first. It removes saved settings and will not fix an upstream router or provider fault.
• Do not permanently disable IPv6 or the firewall as an early fix. That can hide the real cause rather than resolve it.
• Do not download drivers from random driver sites. Use the PC maker, adapter maker, or Windows Update.
• Do not change many settings at once. Retest after each change so you know what helped.
• Do not treat one failed ping as final proof. Some networks block ping; confirm with other diagnostics or a real connection test.

Decision guide: choose the next step

Related reading on Tech World Window

Continue with the guide that matches the layer your tests identified.