Your laptop shows full bars, the network name is right there in the tray, and nothing loads. That gap between “connected” and “online” is the whole problem: your device finished its wireless handshake with the router, but something further along the path is broken.
When Wi-Fi is connected but no internet access appears, the fix depends on one question you can answer in under two minutes: is only one device offline, or is every device offline? One device points at that device’s IP, DNS, or driver state. Every device points upstream at the router, the modem, or the ISP.
At PacketTools, the same diagnostic sequence gets used on production networks: isolate the layer first, then change exactly one thing. Guessing burns an hour. A structured path usually resolves this in ten minutes, and it teaches you where the fault actually lived so you recognize it faster next time.
What a Connected Status Actually Proves
A “connected” indicator confirms one thing: your wireless adapter successfully authenticated to the access point and holds a radio link. It says nothing about whether the router can reach your ISP, whether you received a valid IP address, or whether DNS resolves.
Wi-Fi Association Is Not Internet Reachability
Association happens at layer 2. Your device negotiated the security handshake with the wifi router and joined the wireless network. Internet reachability lives several layers above that, requiring a valid TCP/IP configuration, a working default gateway, and an upstream WAN link that carries traffic.
Windows knows the difference. That yellow warning triangle appears because Windows sends a small probe to a Microsoft connectivity endpoint after joining. When the probe fails, the label changes to “No internet, secured” while the radio link stays perfectly healthy.
The Path From Wireless Device to ISP
Traffic crosses four distinct handoffs before it reaches a web server:
- Device to router: the radio link, plus a DHCP-assigned IPv4 or IPv6 address
- Router internal routing: NAT, firewall rules, and the default gateway
- Router WAN to modem: the physical uplink, often an Ethernet cable
- Modem to ISP: the DOCSIS, fiber, or DSL circuit that carries you to the wider internet
Any one of those four can fail while the first stays green. That is why a single “restart everything” reflex fixes the problem sometimes and wastes ten minutes the rest of the time.
Why Full Signal Bars Can Still Mean No Web Access
Signal bars measure received signal strength from the access point. A router sitting six feet away with a dead WAN port still broadcasts a beautiful five-bar signal.
Strong signal with no traffic also shows up when the router hands out an address from the wrong subnet, when a captive portal login has expired, or when the ISP has suspended the account. In each case, the wi-fi signal is irrelevant to the fault.
How to Locate the Fault in Two Minutes
Three quick tests narrow the fault from “somewhere on the network” to a single component: a second device, a wired connection, and a raw IP ping against a domain name lookup. Run them in that order before touching any network settings.
Check Whether One Device or Every Device Is Offline
Pick up a phone or tablet on the same network and open two familiar sites. Testing two sites matters because a single site can be down while your connection is fine.
If the second device works, leave the router alone and troubleshoot the first device. If nothing works, move upstream to the modem, router, and ISP. This one check eliminates half the possible causes in about thirty seconds.
Compare Wi-Fi With an Ethernet Connection
Plug a laptop directly into a router LAN port with an Ethernet cable and disable the wi-fi adapter. Working wired traffic isolates the fault to the wireless side: radio, band steering, or the wireless adapter itself.
If the wired connection is also dead, the problem sits at the router WAN or beyond. As a hands-on troubleshooting walkthrough puts it, comparing your wired vs. wireless connection tells you whether you are facing a Wi-Fi problem or an internet problem.
Test an IP Address and a Domain Name Separately
Open a terminal and run two pings back to back:
ping 1.1.1.1(a raw IP address, no name resolution involved)ping google.com(requires a working DNS server)
The IP succeeding while the name fails is a textbook DNS failure, and it means your internet connection itself is intact. Both failing points at routing, the gateway, or the WAN link. A browser-based ping test run from another machine confirms whether the destination is reachable from outside your network.
When the Entire Network Has Lost Internet Access
Every device offline means the fault sits at the router, the modem, or the ISP circuit. Work through the power cycle first, read the status lights second, and only then start a conversation with the provider.
Power-Cycle the Modem and Router in the Right Order
Order matters because the modem must complete its ISP handshake before the router requests a WAN address.
- Unplug both the modem and the router.
- Wait two to five minutes so capacitors drain and the ISP releases the old session.
- Plug in the modem alone. Wait until its online or globe light goes solid.
- Plug in the router. Give it another five minutes before testing.
Rushing step three is the most common mistake. A router that boots against a modem still syncing will grab a bogus WAN address and hold it until the next reboot.
Inspect WAN Status, Cables, and Router Indicators
Router indicator colors follow a consistent convention across most manufacturers: green, blue, or white for normal operation, orange or amber for limited connectivity, and red or unlit for no connection at all. A dark globe icon with a healthy Wi-Fi icon is the exact signature of this problem.
Reseat the Ethernet cable between the modem’s LAN port and the router’s WAN port, then check the router’s admin page for the WAN status. An address of 0.0.0.0 or 169.254.x.x on the WAN interface means the router never received an ISP lease.
When to Check for an Outage or Contact the ISP
Escalate once wired and wireless both fail, the modem shows no sync, and a full power cycle changed nothing. Check the ISP’s status page from cellular data, and look for scheduled downtime notices before assuming hardware failure.
Have two details ready: the modem’s light pattern and whether the WAN interface received an address. Those two facts skip most of the scripted first-tier questions.
How to Repair a Single Offline Device
One device offline while everything else works points to a stale saved profile, a bad DHCP lease, a driver fault, or a VPN and firewall conflict. Fix them in that order, since each step takes less time than the one after it.
Forget the Network and Reconnect From a Clean Profile
Saved profiles accumulate stale security parameters, old proxy entries, and outdated band preferences. Removing the profile forces a fresh negotiation.
On Windows 11 and Windows 10, open Settings > Network & internet > Wi-Fi > Manage known networks, select the network, and choose Forget. Reconnect with the password. On iOS and Android, tap the network name and pick Forget This Network.
If that fails, disable and re-enable Wi-Fi entirely, then toggle airplane mode once to reset the radio stack.
Renew DHCP Addressing and Verify the Default Gateway
An address starting with 169.254 means DHCP never answered and Windows self-assigned. Open Command Prompt as administrator:
ipconfig /release
ipconfig /renew
ipconfig /allConfirm the IPv4 address matches your router’s subnet and that the default gateway is the router’s LAN address. Ping that gateway. No reply means the problem is between your wireless adapter and the router, not upstream.
Check Drivers, Services, VPNs, and Firewalls on Windows
Disconnect any VPN client fully, then confirm its virtual adapter is not still holding the default route. Third-party firewalls with a “block all” state after an update produce this symptom on one machine only.
Open Device Manager, expand Network adapters, and update or roll back the Wi-Fi driver. In services.msc, verify WLAN AutoConfig is running and set to Automatic. Disabling fast startup in Power Options resolves the cases where the adapter never fully initializes after shutdown. Run the built-in network troubleshooter last; it repairs the simple cases and names the failing component in the rest.
Use the Right Recovery Steps on macOS, Android, and iPhone
On macOS, remove the network under Wi-Fi settings, then delete mDNSResponder-related caches by restarting. Renewing the DHCP lease sits under Advanced > TCP/IP.
On Android, use Reset network settings from System > Reset options. On iPhone, the equivalent network reset lives under General > Transfer or Reset iPhone > Reset > Reset Network Settings. Both clear saved Wi-Fi passwords, so have credentials ready.
How to Diagnose DNS and TCP/IP Configuration Problems
DNS failures are the single most common cause of a device that pings by IP but loads nothing in a browser. The layer is easy to confirm, easy to flush, and easy to repoint at a public resolver.
Recognize When DNS Is the Only Broken Layer
The signature is exact: ping 8.8.8.8 succeeds, ping google.com returns “could not find host.” Your routing works and your gateway works. Name resolution alone is broken.
A second tell is browsers failing while a VPN, a game client, or an app with hardcoded IPs keeps running. Deeper name resolution faults are covered in our guide to troubleshoot DNS issues.
Flush Stale DNS Cache Entries
A poisoned or stale DNS cache holds expired records that point nowhere. On Windows, open Command Prompt as administrator and run:
ipconfig /flushdnsFollow with netsh winsock reset and netsh int ip reset when the flush alone does not restore access, then reboot. On macOS, restart mDNSResponder with sudo killall -HUP mDNSResponder.
Verify DHCP, IPv4, and DNS Server Settings
Open Network Connections, right-click the adapter, choose Properties, then Internet Protocol Version 4 (TCP/IPv4). In most home setups, both address and DNS should be set to obtain automatically.
Manually specifying a public resolver isolates a broken ISP DNS server:
| Resolver | Primary | Secondary |
|---|---|---|
| Google Public DNS | 8.8.8.8 | 8.8.4.4 |
| Cloudflare | 1.1.1.1 | 1.0.0.1 |
Apply, then flush the cache again before testing. If pages load with the public resolver, the ISP’s DNS was the fault.
Use IPv6 Changes Only as a Controlled Test
Disabling Internet Protocol Version 6 (TCP/IPv6) occasionally clears connectivity on networks advertising IPv6 without working upstream routing. Treat it as a diagnostic step, not a permanent configuration.
Re-enable IPv6 once you identify the real cause. Leaving it off breaks IPv6-only services and masks the underlying router misconfiguration you still need to fix.
Test the Path Before Changing More Settings
Wi-Fi connected but no internet access resolves fastest when you identify the broken layer before touching a setting. One device offline means fix that device’s profile, DHCP lease, or driver. Every device offline means power-cycle the modem first, then the router, and read the WAN status.
The two tests that carry the most weight take under a minute: swap to Ethernet, and ping a raw IP alongside a domain name. Everything after that follows from what those two results tell you.
Once connectivity returns, verify the path from outside your own network. The free network tools at PacketTools run DNS lookups, ping, traceroute, and SSL checks in the browser with no sign-in, no tracking, and no logging of IPs or query data. Confirming that your records resolve correctly with a DNS propagation checker rules out the resolver layer for good, and a quick what is my ip check confirms your public address changed as expected after a modem reboot.
Leave a Reply