Skip to main content
FixMyTech

Wi-Fi Connected But No Internet on Every Device

By

Published

8 min read

Share

Short answer

When every device fails at once the fault is shared, so check the router's Internet / WAN light. Off or red means a line or account problem. Check your provider's status page on mobile data, then power-cycle properly — unplug the modem and router, wait 60 seconds, plug in the modem first and wait for steady lights before the router.

On this page

The lights are on, every device says “Connected”, and nothing in the house can load a web page. The TV cannot stream, phones fall back to mobile data, and the work laptop is useless.

When everything fails simultaneously, that is actually good news diagnostically. It eliminates every device-side cause at a stroke — drivers, saved network profiles, DNS settings on one machine, VPNs. Those cannot all break at the same instant on a phone, a laptop and a smart TV.

The fault is in the shared infrastructure: the router, the modem, or the line into your home.

First, confirm it really is everything

This matters because the fixes are completely different, and router restarts are a waste of an evening if only one machine is affected.

Pick up a phone, disconnect it from Wi-Fi, and check that it works on mobile data. Then reconnect to Wi-Fi and try a website.

What you find Where the fault is What to read
Every device fails on Wi-Fi Router, modem or provider Keep reading
Only one device fails That device’s configuration Connected but no internet
Only the laptop fails Laptop adapter, driver or DNS Works on phone, not laptop
Wired devices work, Wi-Fi does not The router’s wireless side Keep reading, skip the modem
Mobile data also fails Not your network at all A wider provider outage

That last row is worth the ten seconds. If mobile data is also down in your area, you have a regional outage and nothing in your home is broken.

Read the router’s status lights

Before you unplug anything, look at the box. The lights tell you which link in the chain has broken, and that determines everything else.

Most modems and routers carry four meaningful indicators:

Light Solid Flashing Off or red
Power Normal Booting No power, or failed
DSL / Coax / Fibre Line is synced Trying to sync No signal on the line
Internet / WAN / Globe Provider session is up Negotiating No connection to provider
Wi-Fi / WLAN Radio on Traffic passing Wireless disabled

The decisive one is the Internet / WAN light, usually a globe or the word “Internet”.

  • Solid, but nothing works — the router has a connection to your provider. The failure is further out: provider routing, or DNS.
  • Flashing or amber — the modem is trying and failing to establish the session.
  • Off or red — no connection at all. This is a line or account problem. Nothing you do on a device will change it.

If the line light (DSL, coax or fibre) is also out, the physical connection into your home has failed. Reseat the cable at the wall and at the modem, then stop and check for an outage.

Check for an outage before anything else

An hour of troubleshooting your own kit is pointless if the provider is down. Do this on mobile data:

  • Your provider’s app or status page — most will show known outages for your area and often give an estimated fix time.
  • Downdetector or a similar aggregator, which catches outages a provider has not acknowledged yet.
  • Your provider’s social media account, which is usually the fastest to announce a regional fault.

Regional outages produce exactly this symptom and they are far more common than router faults.

Power-cycle in the correct order

If the lights do not point at a line fault and there is no known outage, restart the equipment. Order and timing matter, and doing it wrong is why so many people report that “restarting didn’t help”.

  1. Unplug the modem from power. If you have a combined modem-router from your provider, that is one box and this is the only thing to unplug.
  2. Unplug the router, if it is a separate unit.
  3. Wait 60 seconds. This is not superstition — it lets the provider’s equipment release the old session and lets the modem fully discharge.
  4. Plug in the modem only. Wait until its lights are steady, not flashing. On cable this is typically 2–3 minutes; on fibre or DSL it can be longer.
  5. Plug in the router. Wait another 2 minutes for it to boot and acquire an address.
  6. Test on one device.

Use the power cable, never the reset button. The recessed reset button restores factory defaults — it erases your Wi-Fi name, your password, and any port forwarding or custom DNS you configured. You would then have to set up every device in the house again.

Reseat the cables while it is unplugged

While everything is off, unplug and firmly reconnect:

  • The coax, DSL or fibre lead at the wall socket and at the modem.
  • The ethernet cable between modem and router.
  • The router’s power lead at both ends.

Loose cables are an unglamorous but genuinely frequent cause, especially behind furniture that gets moved or in homes with pets.

Check the router’s admin page

If the router itself is reachable — your devices connect to it, after all — log in and look at its status. The address is usually 192.168.1.1 or 192.168.0.1, and it is printed on a label on the device along with the admin password.

Navigate to Status, WAN or Internet:

  • No WAN IP address shown (blank, or 0.0.0.0) — the router never got a connection from your provider. Line or account problem, confirmed.
  • A WAN IP is present but nothing works — the router has a connection. The problem is the provider’s routing or DNS, or something in the router’s own configuration.

While you are there:

  • Check for a firmware update. Routers left un-updated for years develop exactly this kind of intermittent fault, and most have a one-click update under Administration or System.
  • Check the DHCP pool. If the router hands out, say, 50 addresses and you have 60 devices including every smart bulb and plug, new devices get no address at all. Widen the range or shorten the lease time.
  • Check the DNS settings. If someone configured a DNS server that has since gone offline, every device inherits a broken lookup path. Set it to your provider’s default, or to 1.1.1.1 and 1.0.0.1.

Rule out an address conflict

Two devices with the same IP address knock each other offline intermittently. A single conflict is a two-device problem, but a second router plugged into the network through its WAN port rather than a LAN port creates a second DHCP server and can break the whole network.

Symptoms: devices that work for a minute then stop, different devices failing at different times, and addresses in two different ranges across your devices.

The fix is to make sure only one device on the network runs DHCP. If you have a second router acting as an access point, connect it LAN port to LAN port and turn its DHCP server off in its settings.

Set a reliable DNS at the router

If the WAN light is solid, the router has a WAN IP, and a direct IP address like http://1.1.1.1 loads in a browser while named websites do not — the connection is healthy and DNS is the broken part.

Setting it once at the router fixes it for every device at once:

  • Cloudflare: 1.1.1.1 and 1.0.0.1
  • Google: 8.8.8.8 and 8.8.4.4

Look under Internet, WAN or DHCP settings for DNS server fields. After saving, restart the router and reconnect a device so it picks up the new setting with a fresh lease.

Myths worth dropping

  • “Restart it every day to keep it fast.” A healthy router runs for months. If yours genuinely needs daily restarts, it is failing or overheating — move it somewhere ventilated, and if that does not help, replace it.
  • “Reset to factory settings fixes network problems.” It fixes misconfiguration and nothing else, at the cost of reconfiguring every device you own. It cannot repair a dead line.
  • “Wi-Fi booster apps and extenders will help.” An extender rebroadcasts a signal that already reaches your devices fine. The problem is beyond the router entirely.
  • “Changing the Wi-Fi channel fixes no-internet.” Channels affect speed and stability within your home, not whether traffic reaches the outside world.
  • “Buy a new router.” Possibly, eventually — but only after the WAN light has proved the line is up. Replacing a router when the fault is your provider’s line is an expensive way to change nothing.

When to call your provider

Call when you have evidence, not just a symptom. You will get through the script much faster if you can say:

  • Every device on the network is affected.
  • The internet or WAN light is off, red or flashing.
  • The modem has been power-cycled with a 60-second gap and the light did not change.
  • There is no outage listed for your area.

That set of facts tells them the fault is on their side of the wall, which is exactly where it is.

Realistic expectations

A correctly ordered power-cycle resolves a large share of these within five minutes. A provider outage resolves itself, usually within a few hours.

If the connection comes back but keeps dropping afterwards, that is a different pattern with different causes — Wi-Fi that keeps disconnecting covers intermittent drops across devices, and laptop Wi-Fi keeps disconnecting covers the case where only one machine drops.

Frequently asked questions

What does the router's Internet or WAN light tell me?
Solid means the provider session is up, so the fault is further out in routing or DNS. Flashing or amber means the modem is trying and failing to connect, and off or red means there is no connection at all — a line or account problem.
What is the correct order to restart a modem and router?
Unplug both, wait 60 seconds so the provider's equipment releases the old session, then plug in the modem alone and wait for its lights to go steady. Only then plug in the router and give it two minutes to boot.
Should I press the reset button on my router?
No. The recessed reset button restores factory defaults and erases your Wi-Fi name, password, port forwarding and custom DNS, meaning every device in the house needs setting up again. Always use the power cable instead.
How do I know whether DNS is the problem?
If the WAN light is solid and an address like http://1.1.1.1 loads in a browser while named websites do not, the connection is healthy and DNS is broken. Set Cloudflare or Google DNS once at the router to fix every device at the same time.
Can a second router break the whole network?
Yes. A second router connected through its WAN port runs a second DHCP server, handing out conflicting addresses. Connect it LAN port to LAN port and turn its DHCP server off so only one device assigns addresses.

All Wi-Fi guides