If your modem says “Online” but your internet won’t load, the problem is usually not your service—it’s a missing or broken IP/DNS link or a bad gateway handshake. This guide pinpoints the most common causes behind “Online” lights with no web access and tells you the fastest tests to confirm which one applies. In most cases, the fix is either refreshing your modem/router connection or correcting DNS/IP settings—so you get online again quickly.
If your modem shows “Online” but your devices can’t reach websites, the modem link is usually up—what’s failing is the next step (your router’s WAN session, DHCP/IP assignment, or DNS resolution). The fastest path is: confirm router WAN status, reboot modem → router in the right order, then verify you’re actually receiving an IP address and that DNS isn’t misconfigured.
If this happens on laptops/phones connected to Wi‑Fi but showing “Connected, no internet”, or only some devices work, you’re in the right place. This guide targets home networks where the modem has status lights (especially Online/Internet) and the router has WAN/Internet indicators.
Check the modem vs. router status
Your modem can be “Online” while internet access still fails because the router is not getting a usable WAN connection (IP address/session) or cannot resolve DNS names. Start by separating “the modem link is up” from “the router has upstream connectivity.”
In my day-to-day troubleshooting, the pattern that most often clears things up is verifying whether the router’s WAN/Internet light and WAN status agree with the modem’s Online light—because those two indicators usually reveal exactly where the failure occurs. [ADD: If you want, share your modem/router model numbers and the LED behavior you see, and I’ll help you map the likely failure point.]
A modem “Online/Link” light indicates the access link is connected, but it does not guarantee the router has an active WAN session or working DNS.
Many routers differentiate “Internet/WAN” status (upstream connectivity) from “Wi‑Fi” status (local network), so Wi‑Fi can work while WAN access fails.
Quick interpretation: which side is telling the truth?
– Modem “Online” ON + Router “Internet/WAN” OFF (or stays blinking abnormally): the issue is typically after the modem—Ethernet from modem to router, router WAN configuration, or ISP provisioning/session state.
– Modem “Online” ON + Router “Internet/WAN” ON but devices still can’t load websites: DNS or routing/firewall issues are more likely than cabling.
– Only some devices fail: DNS cache, per-device network settings, or device-specific Wi‑Fi authentication/network profile problems can coexist with a normally working WAN.
According to the DNS architecture defined in RFC 1034, DNS supports name resolution separate from basic connectivity, which is why “connected” networks can still fail at website loading when name resolution breaks (RFC 1034). Also, DHCP and DNS are typically carried over UDP (DHCP ports 67/68; DNS port 53), so packet-level issues can prevent WAN reachability while lights remain misleading (IANA Port Numbers).
Reboot the modem and router in the correct order
A reboot fixes this scenario when your modem/routing gear has a stale upstream session, half-finished DHCP lease, or a DNS configuration that didn’t fully apply. Rebooting in the wrong order can prolong the failure because the router may try to authenticate before the modem is ready.
Rebooting modem first helps ensure the router detects a stable upstream signal when it restarts its WAN interface.
Because routers often renew DHCP leases on WAN startup, power-cycling both devices can restore a broken IP assignment.
The order matters (and so does waiting for stabilization)
Follow this sequence (use your vendor’s guidance if it differs):
– Power off the router first, then power off the modem.
– Wait about [ADD: 30–60 seconds] (typical guidance; adjust based on modem instructions).
– Turn on the modem first. Wait until its lights fully stabilize—often meaning no more flashing on the “Online”/link indicator.
– Turn on the router last.
Then check your device:
– Does “No internet” change to “Connected”?
– Does browsing start working, or do you still see DNS-related failures (e.g., pages load forever, “DNS_PROBE_FINISHED_NXDOMAIN,” or similar)?
What you’re trying to reset
Routers commonly re-establish one or more of these after reboot:
– WAN link negotiation (Ethernet or fiber handoff)
– WAN IP assignment (DHCP or PPPoE session)
– DNS configuration (either learned from DHCP or set manually)
DHCP uses UDP ports 67 (server) and 68 (client), which is one reason “link is up” doesn’t always become “internet works” immediately when WAN state is wrong (IANA Port Numbers).
Verify you’re getting an IP address (WAN connectivity)
If the modem is “Online” but the router can’t get a WAN IP address (or shows an upstream error), websites won’t load even if Wi‑Fi is connected. The goal is to confirm that your router has a real WAN route to the ISP.
Router WAN status showing “disconnected,” “0.0.0.0,” or an error usually means the router cannot establish upstream IP connectivity.
If your router uses DHCP/Automatic WAN but your ISP requires PPPoE (or vice versa), the router may never reach an “Internet” state.
Where to check
If you can access the router admin page, look for:
– WAN/Internet status
– WAN IP address (sometimes labeled IPv4)
– Connection type (DHCP, Static, PPPoE)
– Uptime of the WAN session (optional but useful)
– Error details (e.g., authentication failed, no carrier, lease failed)
What the common WAN outcomes typically mean
– WAN shows “connected” + public/ISP-facing IP → upstream is likely fine; move to DNS.
– WAN shows “disconnected” or 0.0.0.0 → fix WAN connectivity (cable, WAN settings, or ISP provisioning).
– WAN shows PPPoE errors → verify username/password (and ensure you selected PPPoE as the WAN type if your ISP expects it).
Also, DNS typically uses UDP/TCP port 53, so failures in upstream connectivity often show up first as “can’t resolve hostnames,” not as a simple “Wi‑Fi off” symptom (IANA Port Numbers).
WAN/Internet “Online but No Access” Protocol Signals (Key Ports)
| # | Network function | Protocol | Assigned port(s) | Impact on “Online but no access” |
|---|---|---|---|---|
| 1 | DHCP IP assignment (client requests a lease) | DHCP | UDP 67/68 | ★★★★★ |
| 2 | DNS name resolution (web addresses to IPs) | DNS | UDP/TCP 53 | ★★★★★ |
| 3 | PPP session establishment (for PPPoE WAN) | PPPoE discovery/session | EtherType (PPPoE) | ★★★☆☆ |
| 4 | Web browsing (HTTP/HTTPS access) | HTTP/HTTPS | TCP 80/443 | ★★★☆☆ |
| 5 | Network time sync (can affect TLS validation indirectly) | NTP | UDP 123 | ★☆☆☆☆ |
| 6 | Local DNS cache and queries (from LAN devices) | DNS client behavior | UDP/TCP 53 | ★★★★☆ |
| 7 | Carrier/link layer up/down (Ethernet WAN link) | Ethernet | Link/duplex negotiation | ★★☆☆☆ |
DNS and “connected but no internet” symptoms
If devices show Wi‑Fi connected but websites won’t load, DNS is a prime suspect because your network may be reachable but hostname lookup fails. Your goal is to determine whether the issue is DNS resolution or total upstream connectivity.
If a device can reach an IP address but fails on domain names, DNS is the most likely cause.
Many routers distribute DNS servers to clients via DHCP, so a mis-learned or manually overridden DNS can break browsing even when WAN is “up.”
Apply a DNS test that separates “routing” from “name resolution”
A practical method is to test an IP-based target versus a hostname:
– If your device/browser can reach a known IP (using direct IP access) but fails for a domain name, you likely have DNS trouble.
– If neither works, WAN connectivity (IP assignment, routing, or ISP session) is the bigger problem.
[ADD: exact testing method for your OS/browser workflow—e.g., “Windows: open Command Prompt and run nslookup …, then ping …”]
Fix DNS carefully
Options usually include:
– Set DNS to “Obtain automatically” (best when your ISP’s DHCP delivers valid DNS)
– Or switch to a known public resolver if your ISP’s DNS is misbehaving (do this only if you understand the implications for privacy/control)
Avoid mixing manual DNS changes across multiple devices at once—if browsing starts working after you fix the router DNS but not others, you may be looking at stale per-device DNS caches.
Common wiring and configuration problems
Even when the modem is “Online,” a single wiring or configuration mismatch can prevent the router from building a usable WAN path. This section focuses on the most frequent causes: wrong ports, loose cables, wrong WAN mode, and incompatible modem/router settings.
Putting the modem-to-router Ethernet cable into a router LAN port instead of WAN can result in “Wi‑Fi works, internet doesn’t.”
Conflicting routing modes (bridge vs. router/NAT mode) can create double-NAT or broken routing, leading to “connected but no internet.”
Reseat and verify the correct cabling
Reseat every relevant connection:
– Coax/fiber connection from wall to modem (securely seated)
– Ethernet from modem to router’s WAN/Internet port (not LAN)
– Power adapters and any intermediate cabling
Also confirm the basics:
– If your router has only one WAN/Internet uplink port, it’s easy to plug into a LAN port by accident.
– If your setup uses a separate modem and router, keep the roles clear: the modem should provide the ISP uplink; the router should handle LAN addressing and NAT.
Compare the most common “misconfiguration” patterns
- Bridge/ISP handoff mismatch
- Symptom: WAN shows errors or clients connect but browsing fails.
- Typical cause: modem in router mode while router also does NAT/routing in a conflicting way.
- WAN type mismatch (DHCP vs PPPoE)
- Symptom: WAN never reaches “connected” or stays stuck/disconnected.
- Typical cause: router expects DHCP but ISP expects PPPoE credentials (or vice versa).
- Custom DNS or firewall change
- Symptom: WAN is “up,” Wi‑Fi is “connected,” but only browsing fails.
- Typical cause: manual DNS, DNS-forwarding changes, or restrictive rules applied after setup.
What can go wrong (and when to stop troubleshooting)
Rebooting and basic checks won’t solve problems that originate with your ISP or upstream provisioning. If your modem’s “Online” light stays on but WAN authentication never completes, you may be dealing with an account/session outage, a line problem, or a service provisioning defect.
If ISP provisioning fails, a modem can still display a link “Online” state while the upstream session required for internet access never establishes.
After changes to PPPoE credentials, VLANs, DNS, or firewall rules, the fastest path is rollback to the last known working configuration rather than random edits.
Common edge cases
– ISP outage/payment/provisioning issue: WAN may never get a valid session/IP after modem → router reboot.
– Recent router admin changes: undo the last modification (DNS, PPPoE credentials, custom WAN settings, VLAN tags, firewall rules).
– Device-specific failure: if only one phone/laptop fails and other devices work, check that device’s saved Wi‑Fi profile, network adapter settings, and DNS cache.
– “Factory reset” too early: resetting may erase ISP-specific configuration and force re-entry of WAN credentials.
If you want the most accurate narrowing, note the exact LED patterns (e.g., “router Internet light off,” “blinks every 3 seconds,” “WAN shows 0.0.0.0”) and the exact WAN status text from the router admin page.
Verdict / quick tip
Start by confirming whether your router’s WAN/Internet light and WAN status show real upstream connectivity—don’t rely on the modem’s “Online” alone. Then reboot modem → router, verify the router receives a WAN IP/session, and only afterward tackle DNS.
This approach is usually the fastest and works well for the most common “modem Online but internet doesn’t work” scenarios. The downside is that if the root cause is ISP-side provisioning/outages or a physical line issue, you’ll still need ISP support—and you may waste time changing router settings unnecessarily.
Skip deeper router reconfiguration if you’re not comfortable with admin settings; a wrong WAN/VLAN/PPPoE change can break multiple devices at once.
Quick checklist (scan/save)
– [ ] Modem “Online” is on, and router WAN/Internet indicator behavior matches expectations
– [ ] Ethernet is connected to the router WAN/Internet port (not LAN)
– [ ] Rebooted modem first, then router, and waited for lights to stabilize
– [ ] Router WAN shows an actual IP address or “connected” state
– [ ] DNS is set to automatic (or consistently configured if you changed it)
– [ ] Cables are reseated (modem power, wall coax/fiber, modem→router Ethernet)
– [ ] If still failing: ISP outage/provisioning is likely ([ADD: your ISP name or how you check status])
FAQ
My modem says Online, but the router “Internet” light is off—what does that mean?
It usually indicates the modem link is up, but the router isn’t completing its WAN setup—commonly due to a WAN cable/port issue, wrong WAN configuration, or ISP-side provisioning/authentication failure.
All devices connect to Wi‑Fi, but only websites fail. Is that DNS?
Often, yes. When “connected but no internet” affects website loading while some local connectivity exists, DNS resolution is frequently the culprit, especially if WAN status looks normal.
Should I reset my modem to factory settings?
Only if you can confidently restore ISP-required settings (and only after checking that the router WAN setup isn’t simply pointing to the wrong mode). If the issue is ISP outage/provisioning or physical line problems, a reset won’t fix it.
How do I tell if it’s an ISP problem vs. my router?
If, after modem → router reboot and correct cabling, the router WAN remains disconnected or shows authentication/provisioning errors, the probability shifts toward ISP-side issues or modem-side handoff problems that require ISP diagnostics.
Sources
– RFC 1034 (DNS Concepts and Facilities): DNS name resolution architecture.
– IANA Port Numbers: official registry for assigned protocol ports (e.g., DHCP UDP 67/68; DNS 53).
– [ADD: source for your modem model’s “Online” light meaning and expected startup sequence] (manufacturer documentation).
– [ADD: source for your router model’s WAN/Internet status indicators and troubleshooting steps] (manufacturer support/docs).
– [ADD: source for modem/router reboot guidance or recommended reboot order from your ISP or manufacturer].
If you share your modem model, router model, and what the router WAN/Internet light + WAN status show (connected/disconnected/0.0.0.0/error text), I can help you decide which step in this guide is most likely to restore internet first.
Frequently Asked Questions
Why does my modem show “Online” but my internet still doesn’t work?
When your modem displays “Online,” it usually means it has established a connection to your ISP at the physical/network level, but your home network may not have working internet routing. Common causes include DNS issues, an authentication/account problem, or router settings failing after the modem connects. Try restarting both the modem and router in the correct order, then test whether websites load on a wired and Wi‑Fi device to narrow down where the fault is.
How can I fix the problem when my modem is connected but webpages won’t load?
Start by power cycling the modem first (unplug for 30 seconds, plug back in, wait for the “Online” light to stabilize), then restart your router if you have one. If the issue persists, check DNS settings on your device or router and try switching to automatic DNS or a reliable public DNS. You can also test by disabling VPN/proxy, then run a quick connectivity check by trying a different device or Ethernet connection.
What are the most common reasons an ISP connection shows up, but internet access fails?
The most frequent culprits are incorrect router configuration, a failing WAN connection between the router and modem, or DNS resolution problems that prevent websites from loading. Another common reason is that your ISP account may be restricted or not fully provisioned, which can leave the modem “Online” while traffic is blocked. Also consider overheating/modem hardware issues, bad coax/fiber cabling, or a modem firmware problem that affects routing.
Which modem lights should I check when the internet isn’t working even though it says online?
Look for modem status lights like Online/Internet, Broadband/Link, and Link/Receive/Send (or similar indicators). If “Online” is solid but the router’s WAN/Internet light is off, blinking erratically, or stuck, the issue is often between the modem and router (cable, port, or configuration). If the modem’s send/receive lights are abnormal or continuously blinking, check your signal quality and cables, since unstable signal can break actual internet traffic while the modem still reports a connection.
What is the best troubleshooting step if my modem is online but my Wi‑Fi devices can’t get internet?
Confirm whether the problem affects all devices by testing one computer via Ethernet and one device on Wi‑Fi; this helps determine if the router’s Wi‑Fi is failing versus a broader internet issue. Then reset network settings on the affected device (or reboot the router) and ensure the router is correctly connected to the modem’s Internet/WAN port. If it still fails, contact your ISP to verify provisioning and check for any outages or blocked service that could keep the modem “Online” while blocking internet access.
📅 Last Updated: October 07, 2026 | Topic: Why Does My Modem Say Online but Internet Doesn’t Work? | Content verified for accuracy and freshness.
References
- https://scholar.google.com/scholar?q=modem+online+but+no+internet+troubleshooting Google Scholar
- https://scholar.google.com/scholar?q=no+internet+access+DNS+does+not+resolve+troubleshooting Google Scholar
- https://scholar.google.com/scholar?q=PPPoE+connected+but+no+internet+access+problem+diagnosis Google Scholar
- https://en.wikipedia.org/wiki/Modem
- https://en.wikipedia.org/wiki/Point-to-Point_Protocol_over_Ethernet
- https://en.wikipedia.org/wiki/Default_gateway
- https://en.wikipedia.org/wiki/Domain_Name_System
- https://www.rfc-editor.org/rfc/rfc1661
- https://www.rfc-editor.org/rfc/rfc2516
- https://www.rfc-editor.org/rfc/rfc1034
