If router connected but no WAN IP, compare one working device, app, port, cable or connection type against the failing one before resetting anything.
Then check IP address, gateway, DNS, saved network settings, VPN or filtering, firmware, and provider-side clues in that order.
The status message is only the first clue
When router connected but no WAN IP, the device is usually telling only half of the story. Something is connected, but not necessarily connected all the way to the internet. A router can see the modem but fail to receive a WAN address. Windows can browse the web while its own status probe says offline. A Fire TV can join Wi-Fi but fail the internet check. An ONT can show Ethernet link while the provider session is not complete. A USB adapter can associate with Wi-Fi but miss DHCP, DNS, or a driver step. The useful move is to stop treating the symptom as one big mystery and split the path into smaller handoffs.
This guide follows that handoff. First, compare one working path with the failing one. Then check the local connection, IP address, DNS, saved network state, firmware, and provider clues. That order is slower than pressing every reset button in sight, but it gives you a cleaner answer and avoids creating new problems while trying to fix the old one.
Quick diagnosis table
Try these fixes in order
Work through these checks in order. Each one proves a different handoff in the connection path.
- 01
Confirm exactly what is connected
Check whether the device is connected to Wi-Fi, Ethernet, the router, the modem, or only a local network. The word connected is vague, so match it with a real test like opening the router page or checking WAN status.
- 02
Compare one known-good path
Use another device, another port, another cable, or another Wi-Fi band as your control. If the other path works, you can narrow the fix instead of blaming the whole network.
- 03
Restart in the correct order
For home internet equipment, restart the modem or ONT first, wait for its main lights to settle, then restart the router, then the affected device. This rebuilds the path from the provider inward.
- 04
Check IP address and gateway
A device can be connected locally and still have no useful IP address or default gateway. A 169.254 address, blank gateway, or missing WAN IP is a strong clue that address assignment failed.
- 05
Return DNS to automatic for one test
Custom DNS can help in some cases, but it can also hide the real problem. Test automatic DNS first, then try a trusted public DNS only if the symptom points to name lookup failure.
- 06
Disable VPN, proxy or filtering briefly
VPNs, proxy settings, parental controls and security filters can block traffic while the network still looks connected. Disable only what you are allowed to disable, then test the exact symptom again.
- 07
Check firmware or driver updates
Routers, streaming devices, adapters and Windows network components can all develop connection bugs after updates or long uptime. Update the right device only after the basic path checks make sense.
- 08
Escalate with evidence
If several devices fail, modem or ONT lights look wrong, or the router never receives upstream service, contact provider or device support with your notes. Exact symptoms beat a vague complaint every time.
Detailed checks
Connected is not the same as online
Connected usually means one local link worked. Online means the device can pass traffic through the router, DNS, modem or ONT, provider network and the wider internet.
- This difference explains most confusing home network messages. The status is not always lying; it is just describing a smaller part of the path.
The first comparison matters most
A second device or second connection path is your fastest shortcut. If another device works on the same network, the internet service is probably alive. If every device fails, move upstream.
- Make the comparison from the same room or same router port when possible. Otherwise you may mix a device issue with a range issue.
IP address problems are common
If the device or router cannot get a valid address, the connection can look active without internet. This happens with stale leases, bad cables, router DHCP trouble, MAC locks, bridge mode mistakes and adapter driver issues.
- Do not skip this check. It often tells you whether the failure is local, router-side or provider-side.
DNS can create a false internet failure
DNS turns names into addresses. When DNS fails, apps and browsers may act as if the internet is gone even when some raw connectivity still works.
- That is why a DNS issue can affect one device, one app, or Windows status while other traffic behaves differently.
Saved profiles can become stale
Phones, TVs, adapters and computers remember network names, passwords, security modes and private address details. After a router change or update, that memory can become a trap.
- Forgetting the network and joining again is often safer than wiping the router.
Firmware and drivers belong later
Updates are useful, but they are not the first move unless the symptom began immediately after an update. Check cables, address assignment, DNS and comparison tests first.
- Then update the exact device involved: router firmware for router-wide issues, adapter drivers for one computer, or device software for Fire TV and similar hardware.
Know when it is not your side
If modem, ONT, PON, LOS, broadband, online or WAN lights never settle, the problem may be outside your device. The same is true when several devices fail after clean restarts.
- At that point, support should check activation, provisioning, signal level, account status or line condition.
Mistakes to avoid
Do not assume connected means fully online.
Do not change several settings at once.
Do not call the provider without noting which devices, lights or paths failed.
FAQ
Why does router connected but no WAN IP happen?
It happens because one step in the connection works while a later step fails. The device may have local link, but not IP, DNS, WAN access, app validation, or provider service.
That is why the fix starts with comparison. You need to know which handoff failed before resetting shared equipment.
Should I factory reset the router?
No, not first. A factory reset erases settings and can make the network harder to restore, especially if the real problem is one device, one cable, one adapter, or the provider handoff.
Use a normal restart, IP/DNS checks, saved-network cleanup and another-device comparison before factory reset enters the conversation.
How do I know if it is my device or the whole network?
Test another device on the same network and, if possible, test the failing device on another network. If only one device fails, the fix should stay close to that device.
If several devices fail together, check router, modem, ONT and provider clues instead of reinstalling one adapter or app.
Can DNS cause this symptom?
Yes. DNS can make websites, apps or Windows status fail while the basic connection still appears active.
Try automatic DNS first. If automatic DNS fails and IP connectivity looks normal, testing a trusted public DNS can help confirm the clue.
Can a VPN or security app cause it?
Yes. VPNs, proxies, parental controls and security filters can intercept traffic in ways that make the network look connected but unusable.
Disable only what you are allowed to disable. If the connection returns, fix that tool's settings rather than replacing hardware.
When should I call support?
Call support when several devices fail, the modem or ONT lights are abnormal, the router cannot get a WAN address, or the issue continues after clean restart and cable checks.
Bring notes: exact error, device model, affected devices, light status, time of failure and what you already tested.
Do I need new equipment?
Not immediately. Many connected-but-no-internet problems come from setup state, stale profiles, DNS, DHCP, firmware or cable handoff issues.
Replace equipment only after the symptom repeats under normal conditions and you have proved the smaller fixes do not hold.
What is the safest first fix?
The safest first fix is a comparison test. Check one working path against the failing path, then restart in order if multiple devices are affected.
That gives you useful information without erasing passwords, router names, app logins or device settings.
Outside references
- NETGEAR router support
Official support reference for checking device, router, adapter or provider-specific settings.
- TP-Link router support
Official support reference for checking device, router, adapter or provider-specific settings.