Router Won't Connect to the Internet (No Internet, Connected): The Real Fix

Your Wi-Fi icon says "connected." Every bar is full. And yet nothing loads — not a search, not an email, not a single page. It's one of the most annoying messages in home networking, mostly because "connected" feels like it should mean the internet works. It doesn't.

Quick answer: "Connected, no internet" means your device successfully reached your router, but your router (or the modem behind it) can't reach your internet provider. The fix almost always lives in one of three places — the router-to-modem connection, the modem-to-ISP connection, or a stuck DHCP/DNS setting — and you can usually find which one in under five minutes by working through the checks below in order.

I've run this exact troubleshooting sequence more times than I can count, on everything from a $40 travel router to a mesh system with six nodes, and the cause is almost never exotic. It's a stuck lease, a dead modem handshake, or an ISP hiccup nobody warned you about.

What "Connected, No Internet" Actually Means

Your home network has two separate jobs, and this error tells you exactly one of them is failing:

1. Local connection — your phone or laptop talking to your router over Wi-Fi or Ethernet. This part is working. That's why you see "connected."
2. WAN connection — your router talking to your modem, and your modem talking to your ISP's network. This is the part that's broken.

So the message is really telling you: local network, fine. Path to the outside world, broken. Depending on your device or OS, you might see this phrased as "No internet, secured," "WiFi has no internet access," or a small yellow triangle over the Wi-Fi icon. They all point to the same break.

First: Is It One Device or Every Device?

This single question saves the most time, so check it before touching any settings.

Symptom	Likely cause	Where to look
Only one phone/laptop shows no internet, others are fine	Device-level issue — bad DNS cache, stuck IP lease, driver	Skip to the device fixes below
Every device on the network is affected	Router, modem, or ISP issue	Start with the physical checks and power cycle
Wi-Fi devices affected, but a wired Ethernet device works fine	Wi-Fi radio or band-specific problem on the router	Try the other Wi-Fi band (2.4GHz vs 5GHz), then restart the router
Nothing works even wired directly into the modem	ISP outage or modem fault	Contact your ISP, check outage map

Step-by-Step Fix (In the Order That Actually Works)

1. Check the Physical Connections and Lights

Before any software fix, look at the hardware. It's the most-skipped step and the most common actual cause.

• Confirm the cable from the wall (coax, fiber, or DSL line) is fully seated in the modem.
• Confirm the Ethernet cable between modem and router is in the router's WAN/Internet port, not a LAN port — this is a surprisingly common mix-up after someone unplugs and reconnects cables.
• Look at the modem's internet/online light. Solid green or white usually means a good ISP connection. Blinking red, solid red, or amber typically signals a failed handshake with your provider.
• On the router, an amber or red WAN light — separate from the Wi-Fi light — points to the same thing: it isn't hearing back from the modem or ISP.

2. Power Cycle the Modem and Router — Correctly

Almost every guide says "restart it," but the order and timing matter more than people think.

1. Unplug the modem and the router from power. If they're one combo unit, just unplug the single device.
2. Wait a full 30 seconds. This clears temporary memory and forces a fresh handshake, not just a reboot.
3. Plug the modem back in first. Wait until its lights fully stabilize — usually 1–2 minutes. Don't rush this part; a modem that hasn't finished re-registering with the ISP will hand the router a bad connection.
4. Plug the router back in. Give it another 1–2 minutes to boot and re-establish its WAN connection.
5. Reconnect a device and test.

This single sequence resolves the majority of "connected, no internet" cases, mostly because it forces the modem to re-authenticate with the ISP and grab a fresh IP address.

3. Rule Out an ISP Outage

If the power cycle doesn't fix it, stop troubleshooting your own equipment for a minute and check upstream:

• Use your phone's cellular data (Wi-Fi off) to check your ISP's outage map or status page.
• Call or text your provider's support line — most now have automated outage checks by phone number or address.
• If you have a modem-only setup, connect a laptop directly to the modem via Ethernet, bypassing the router entirely. If that also shows no internet, the problem is upstream of your router and there's nothing on your end to fix except wait it out or call it in.

4. Release and Renew the IP Address (Device-Level Fix)

If only one device is affected, its IP lease from the router may be stuck or conflicting with another device.

Windows:

1. Open Command Prompt.
2. Run ipconfig /release, then ipconfig /renew.
3. Optionally follow with ipconfig /flushdns.

Mac:

1. System Settings → Network → Wi-Fi → Details.
2. Click "Renew DHCP Lease" under TCP/IP.

Android / iPhone:

1. Forget the Wi-Fi network under Wi-Fi settings.
2. Reconnect and re-enter the password fresh — this forces a new IP lease rather than reusing a stale one.

5. Change Your DNS Server

A dead or overloaded DNS server can produce exactly this symptom: connected, but nothing resolves. Switching to a public DNS server is a low-risk fix that takes under a minute.

• Google DNS: 8.8.8.8 / 8.8.4.4
• Cloudflare DNS: 1.1.1.1 / 1.0.0.1 (Learn more on Cloudflare's DNS Explainer)

You can set this on the individual device (network adapter settings) or on the router itself under WAN/Internet settings, which applies it to every device at once.

6. Check for a MAC Address or DHCP Conflict on the Router

Some ISPs bind your internet service to the MAC address of the very first device that connected — often the old router. If you swapped routers recently, or restored one from a backup config, this can quietly block the new device from getting an internet handshake even though Wi-Fi itself works fine.

Fix: log into the router's admin page and look for a "Clone MAC Address" or "MAC Clone" option under WAN settings, and clone your computer's MAC address, or simply power cycle the modem after connecting the new router — this often re-registers the new MAC automatically. (For more details, see the HowToGeek MAC Address Guide).

7. Factory Reset as a Last Resort

If nothing above works and the issue only started after a settings change, firmware update, or power outage, a factory reset clears out any corrupted configuration.

• Hold the reset pin for 10–15 seconds (check your model — some Netgear and Asus units need up to 30).
• This wipes your Wi-Fi name, password, and any custom settings, so only do this after backing up your config if your router supports it.
• After reset, set the router up again from scratch rather than restoring an old backup, since a corrupted backup can reintroduce the same problem.

Router Light Meanings at a Glance

Light	Color / Pattern	What it means
Power	Off or blinking red	Power supply or internal fault
Internet/WAN	Solid green/white	Good connection to modem/ISP
Internet/WAN	Blinking red or amber	Failed handshake — modem or ISP issue
Internet/WAN	Off	No cable connection detected in WAN port
Wi-Fi/wireless	Solid, no internet light lit	Local network fine, WAN side is the problem

Modem vs. Router: Why the Distinction Matters

A lot of "router won't connect to the internet" searches are actually modem problems wearing a router's name tag. The router's only job is to create your local Wi-Fi network and hand out IP addresses to your devices — it has no control over whether your ISP is delivering a signal. If the modem never gets a valid connection from your provider, the router will faithfully create a working local network that simply has nowhere to send your traffic. That's exactly what "connected, no internet" looks like from your phone.

If you have a combo modem-router unit, this distinction blurs, but the same order of checks still applies: rule out the ISP/line issue before touching Wi-Fi settings.

Frequently Asked Questions

The Bottom Line

"Connected, no internet" is a WAN problem dressed up as a Wi-Fi problem. Work the checks in order — physical connections, a proper power cycle, ISP outage check, then device-level DNS/IP fixes — and you'll find the break well before you need to call support or reset anything.