Why Does My Modem Work but Router Doesn’t? Troubleshooting Steps

If your modem works but your router doesn’t, the problem is almost always in the router’s WAN setup or its ability to authenticate with your ISP. You’ll learn the fastest troubleshooting steps to confirm the modem-to-router connection, verify the correct WAN mode and credentials, and isolate whether the issue is wiring, configuration, or a faulty router. Follow this sequence and you can determine what’s blocking internet access in the next few minutes—not the next few days.

If your modem works but your router doesn’t, the most common cause is that the router isn’t getting a valid internet connection from the modem (or it’s not using the correct WAN setup). Start by checking the router’s WAN/Internet status lights and then verify the router’s connection mode (DHCP vs PPPoE), because a small settings mismatch can make the router fail even when the modem sync is fine. This guide will walk you through the fastest checks to pinpoint where the connection is breaking.

This is for anyone who can load the internet directly from the modem (or sees modem “online” indicators) but gets no internet—or no connection—on Wi‑Fi/ethernet through the router. It’s especially useful if the router is new, you recently changed ISP equipment, or you updated router firmware.

Check the modem-to-router link first

Confirm the router is physically and electrically seeing the modem on the correct WAN/Internet port. In most modem→router setups, the router will stay “No Internet” even when the modem has working service if the WAN link isn’t negotiated properly.

If the router’s WAN/Internet port link light never comes on, the router may not be establishing the layer-2 connection it needs to obtain an IP lease from the modem/ONT.

Correct cabling matters: the modem/ONT side typically goes to the router’s WAN/Internet port, not any LAN port.

Power-cycling “modem first, router second” aligns with how many ISP gateways bring up session state after reboot.

What to do (fast physical validation)

– Confirm the WAN port and cable type: Connect the modem (or ONT) to the router’s WAN/Internet port using the correct Ethernet cable (usually Ethernet). Many routers have distinct colors or labels—WAN/Internet should be used for the modem uplink.

– Check WAN/Internet link lights: Look for steady/blinking WAN link activity. If the WAN link light is off or never negotiates, the router can’t move past “no internet” even with a perfectly working modem.

– Try a different port/cable: If your router has multiple LAN ports and only one WAN port, test:

– a different Ethernet cable (to rule out a bad lead),

– and, if supported by your hardware, a different WAN/LAN port for troubleshooting (some models let you test WAN behavior more flexibly).

Power-cycle in the right order

A clean reboot sequence prevents session mismatches:

1. Power off the modem/ONT, wait for all lights to settle (often 30–60 seconds).

2. Power on the modem/ONT and wait until it reaches a stable “online/sync” state.

3. Power on the router and wait for the WAN state to populate.

This aligns with typical ISP behavior where session establishment (DHCP lease or PPPoE session) can fail if the downstream router boots first.

Quick reference: WAN checks that commonly unblock service

Below is a concise table of high-value checks and the specific protocol datapoints they target—use it to avoid random guessing.

Verify router WAN settings (DHCP vs PPPoE)

Most “modem works, router doesn’t” cases come down to the router using the wrong WAN connection type. DHCP vs PPPoE is the single highest-signal setting because it determines how the router obtains an internet session and IP parameters.

DHCP relies on the router requesting an IP lease from the WAN side, while PPPoE requires the router to establish a PPPoE session using ISP credentials.

If your ISP requires PPPoE and the router is set to DHCP, the router can show “No Internet” even when the modem/ONT is online.

If your ISP uses DHCP and the router is set to PPPoE, the WAN IP/DNS fields typically won’t populate.

How to choose the right mode

– If your ISP uses DHCP:

– Set WAN connection type to DHCP (or “Automatic IP” / “Dynamic IP”).

– Avoid entering static WAN IP details unless your ISP explicitly told you to.

– If your ISP uses PPPoE:

– Set WAN connection type to PPPoE.

– Enter PPPoE username and password exactly as provided by your ISP.

– Confirm “Connection mode” behavior (commonly Always On vs On Demand vs Auto). Many ISPs still expect the session to be initiated correctly, even when the modem is physically online.

Data points that matter when choosing DHCP vs PPPoE

– According to RFC 4632 and related DHCP specifications, DHCP uses leases to deliver IP address and network parameters (router WAN values should fill in after the lease).

– According to RFC 2516, PPPoE establishes a PPP session over Ethernet using discovery and session stages; credentials mismatches prevent session establishment.

– According to Ethernet and IP defaults (RFC 791 and common network practice), a typical IP MTU assumption is 1500 bytes—PPPoE can reduce effective payload MTU by 8 bytes (see the MTU check below).

Compare what your router thinks is happening

Your router’s status page (WAN IP, default gateway, DNS) reveals whether the failure is at the WAN negotiation stage or after IP assignment. If the router claims it’s connected but clients can’t reach the internet, the problem often narrows to DNS or gateway reachability.

A blank or “0.0.0.0” WAN IP/DNS on the router usually means the router never obtained a usable WAN lease from the modem/ONT.

If a wired LAN device receives an IP from the router but has no internet, the router’s WAN path is likely failing rather than Wi‑Fi.

WAN IP, default gateway, and DNS are the three fields you check first because they represent addressability, routing, and name resolution.

What to check on the router UI

Look for a Status page or Internet/WAN overview that shows:

– WAN IP address (should be a real public or ISP-provided address; “blank/zeros” is a red flag)

– Default gateway

– DNS servers

If WAN IP and DNS don’t populate after the modem is online and the WAN mode is correct, the router likely can’t complete the session (wrong DHCP/PPPoE settings, missing PPPoE credentials, or ISP-side restrictions).

Test wired vs Wi‑Fi (to isolate scope)

– Use a wired device: Plug a laptop/desktop into a LAN port on the router and confirm:

– Does it get a local IP address via the router’s DHCP server?

– If it does, can it browse websites (not just ping local IPs)?

This helps distinguish:

– WAN failure (router can’t reach the internet)

– Wi‑Fi-only failure (router is fine, wireless is misconfigured)

Comparison: what your router’s signals typically mean

Here’s a parseable comparison that you can map directly to troubleshooting actions:

What you see on router status	Common meaning	Next step
WAN IP/DNS blank or 0.0.0.0	WAN lease/session didn’t complete	Re-check DHCP vs PPPoE + WAN credentials
WAN shows IP but DNS blank	Router can reach ISP but can’t resolve names	Check DNS settings: “auto” vs manual, ISP DNS vs public DNS
LAN devices get IP but no internet	WAN connectivity or routing failing	Confirm default gateway and check NAT/router mode

Power, resets, and firmware issues to rule out

Restarting fixes many issues, but factory resetting can also erase working WAN parameters you don’t want to retype. A disciplined approach—restart first, then reset only after WAN settings are confirmed—prevents churn.

Restarting a router preserves configuration, while a factory reset clears settings that may be required for the ISP WAN method (DHCP vs PPPoE).

Router firmware updates can improve compatibility, but interrupted updates can also corrupt settings, especially on systems with changed WAN modes.

After a factory reset, re-enter only the ISP-required WAN parameters and re-run the router’s ISP setup wizard if available.

Restart vs reset (in the right order)

1. Restart (recommended first):

– Power off the router only (keep modem online if it’s already stable).

– Wait for the router to reacquire WAN.

2. Factory reset (use sparingly):

– Do this only if:

– you’ve confirmed the physical WAN link is correct,

– you’ve verified DHCP/PPPoE settings,

– and the issue persists after restart.

Firmware update guidance

If you recently updated router firmware—or the router is new and unconfigured—updates can still help, particularly for compatibility with ISP gateways/ONTs. However:

– Only update through official router admin pages.

– Avoid power interruptions during the update process.

If your router supports an ISP compatibility wizard, use it carefully. It may help in DHCP environments, but PPPoE environments often require exact credential entry.

What can go wrong (common mistakes and edge cases)

Even with modem “online,” the router can still fail due to configuration mismatches, wiring errors, or special ISP requirements. These edge cases are the ones that waste the most time—so it’s worth checking them early.

Using a LAN-to-LAN cable instead of modem-to-WAN can leave the router’s WAN light off and prevent any internet session from forming.

Double-NAT or conflicting gateway modes (router vs modem/bridge) can break connectivity or make it appear intermittent.

DNS misconfiguration can produce a symptom of “internet unavailable” even when WAN connectivity exists.

Common mistakes to look for

– Modem “works” but expects a specific router WAN method: Some ISPs bind service behavior to PPPoE settings, VLAN tagging, or ONT-to-router expectations. If PPPoE or specific VLAN behavior is required, generic “auto-detect” may not succeed.

– Wrong WAN port selection:

– Modem/ONT should connect to router WAN/Internet.

– Modem/ONT should not connect to a router LAN port unless your ISP explicitly instructs a different topology.

– Double-NAT / wrong operating mode:

– If the ISP equipment is already routing, your router should often be configured as an access point or bridge-friendly setup (depending on ISP guidance).

– DNS confusion:

– If your router can reach the WAN but DNS is wrong/blocked, web browsing fails while some connectivity checks may appear inconsistent.

– Wi‑Fi-only troubleshooting can mislead:

– If ethernet also fails, concentrate on WAN mode and status—not SSID/password.

PPPoE MTU edge case (why “everything looks connected”)

If PPPoE is in play, incorrect MTU/MSS values can cause browsing failures or timeouts even though the session is “up.” A widely used rule is:

– PPPoE overhead can reduce effective MTU by 8 bytes, so an MTU of 1500 may translate to 1492 effective payload on the PPPoE link.

For standards grounding, see RFC 2516 (PPPoE) and general IP MTU behavior RFC 791.

Verdict / tip: the fastest path to the fix

Start with the physical link (cables and WAN/Internet light), then confirm the router’s WAN connection type (DHCP vs PPPoE) and check whether the router actually receives a WAN IP/DNS. If WAN stays blank or the router shows “connected” but clients get no internet, the next best step is to re-check ISP-specific settings or run the router’s ISP setup wizard; if that still fails, consider whether your ISP account is restricting service to a specific device and whether you need to call support.

Downside: if your ISP uses PPPoE/static IP binding, generic router “auto-detect” wizard flows may not solve it—you’ll likely need the exact ISP parameters. Skip this approach (and go straight to ISP/router documentation or support) if you don’t have any modem/ISP access details or if your ISP requires account-specific activation steps.

Quick checklist (scan/save)

– WAN/Internet light on the router is on (or blinking) after connecting to modem

– Modem is fully online before router boots

– Router WAN type is correct: DHCP or PPPoE (per your ISP)

– Router WAN page shows a WAN IP/DNS (not blank/zeros)

– Wired test (LAN port to a device) also fails → issue is likely WAN settings

– Restart worked? If not, verify cables/ports, then consider factory reset + reconfigure

FAQ

My modem has internet, but my router says “No Internet.” What’s the first thing to check?

Check the router’s WAN/Internet status lights and whether the router’s WAN IP/DNS are actually being assigned. If the WAN values are blank, the router isn’t successfully getting a valid connection from the modem.

Do I need to reset my router to fix this?

Not usually. Restarting in the correct order and verifying WAN settings (DHCP vs PPPoE) solves most cases. Factory reset can help when settings are corrupted or unknown, but it’s only worth it after you confirm the WAN configuration and cabling.

Can a bad Ethernet cable make this happen?

Yes. If the WAN port isn’t linking properly, the router can show “no internet” even when the modem is fully online. Testing a different cable is a quick way to rule that out.

If my devices get an IP address from the router, why is there still no internet?

That pattern often means your router is assigning local DHCP addresses, but it can’t complete the WAN connection to the ISP (wrong WAN mode, bad PPPoE credentials, or ISP lease/DNS issues).

Will firmware updates fix modem/router mismatches?

Firmware can help with compatibility, but it won’t replace incorrect WAN settings or ISP account requirements. Update only after you verify the WAN configuration basics.

Sources

– ADD: Source for your router brand/model WAN/Internet connection type settings—use the manufacturer’s official user guide or support page for DHCP vs PPPoE.

– ADD: Source for your modem/ISP equipment regarding whether the modem provides DHCP and whether the router should use DHCP or PPPoE—use your ISP’s official setup/activation instructions or modem/router compatibility documentation.

– ADD: Source for router status page/WAN IP troubleshooting—use the router manufacturer’s official documentation for “WAN IP/DNS,” “Internet connection status,” and DHCP lease behavior.

– RFC 2516 (PPPoE specification)

– RFC 791 (IPv4)

The fastest way to resolve “modem works but router doesn’t” is to treat the problem as a WAN negotiation failure: confirm the modem-to-WAN link first, then verify the router is in the correct WAN mode (DHCP vs PPPoE) and that WAN IP/DNS populate on the status page. Once you narrow where the WAN chain breaks—cabling, WAN mode/credentials, or DNS/routing—you avoid unnecessary resets and get service restored with the least trial-and-error.

Frequently Asked Questions

Why does my modem show an internet connection but my router doesn’t work?

This usually means the modem is syncing and getting internet from your ISP, but the router isn’t successfully creating a local network or WAN connection. Common causes include incorrect router WAN settings, a bad Ethernet cable between modem and router, or the router not receiving the correct IP address (DHCP/PPPoE issues). Restarting both devices in the right order and verifying WAN connection status often pinpoint the problem quickly.

How can I tell if the issue is with my router WAN connection or my ISP modem line?

First, check whether your modem has an active “Internet” or “WAN” light while the router’s “Internet” light stays off. Then connect a device directly to the modem (or use the router’s diagnostic/WAN status page) to confirm whether internet works at the modem level. If internet works when directly connected to the modem but not through the router, the problem is typically the router configuration, WAN setup, or cabling.

What settings should I check on my router when it won’t connect even though the modem works?

Verify the router’s WAN type matches what your ISP requires (DHCP for many cable setups, or PPPoE/Static IP for some). Check whether “Get IP automatically” is enabled when DHCP is expected, and confirm PPPoE username/password if you use PPPoE. Also ensure the router’s firmware is up to date and that MAC address cloning (if used) matches your ISP’s requirements.

Best way to troubleshoot a modem works but router doesn’t situation—what steps should I follow?

Start by power-cycling in this order: unplug modem and router, wait 30 seconds, plug in the modem first and wait for it to fully sync, then plug in the router. Replace the Ethernet cable from modem to router to rule out a physical connection issue, and check the router’s WAN/Internet indicator for link activity and IP assignment. If the router still can’t obtain an IP, log into the router and run the connection test or reset WAN settings to defaults before re-entering any required ISP credentials.

Which cables, lights, and indicators confirm the router is failing to get internet from the modem?

Look for an Ethernet link light between the modem and router—if the link light is off, it’s usually a cable or port problem. If the modem’s Internet light is solid but the router’s Internet/WAN light is off or blinking, the router likely isn’t receiving an IP address or isn’t configured correctly for the WAN type. Checking router logs (or diagnostic pages) for “no IP address,” “authentication failed,” or “WAN connection failed” can help you identify whether the issue is DHCP, PPPoE credentials, or network settings.

📅 Last Updated: October 07, 2026 | Topic: Why Does My Modem Work but Router Doesn’t? | Content verified for accuracy and freshness.

---

References

1. https://scholar.google.com/scholar?q=modem+works+but+router+doesn%27t+troubleshooting  Google Scholar
2. https://scholar.google.com/scholar?q=router+not+working+DHCP+default+gateway+DNS+issues  Google Scholar
3. https://scholar.google.com/scholar?q=PPPoE+modem+router+bridge+mode+troubleshooting  Google Scholar
4. https://en.wikipedia.org/wiki/Modem
5. https://en.wikipedia.org/wiki/Router
6. https://en.wikipedia.org/wiki/Home_networking
7. https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol
8. https://en.wikipedia.org/wiki/Default_gateway
9. https://en.wikipedia.org/wiki/Network_address_translation
10. https://en.wikipedia.org/wiki/Point-to-Point_Protocol_over_Ethernet