Why is My Router Connected But No Internet? 10 Quick Solutions

 This is the most confusing network symptom there is, and the reason is straightforward: your device is telling you the truth, and it is only telling you half the story.

"Connected" means your device successfully joined the local network. It found the router, negotiated a link, and probably received an IP address. That is all it means. Whether the router can then reach the outside world is a completely separate question that your Wi-Fi icon knows nothing about.

This guide works through why your router connected but no internet message appears, and ten solutions ordered by how likely each is to be the actual cause.

First, Confirm What Is Actually Broken

Thirty seconds of checking saves twenty minutes of random fixes.

Open a command prompt and run three commands:

ipconfig
ping 8.8.8.8
nslookup google.com

Now read the results together:

• ping 8.8.8.8 succeeds but nslookup fails — your internet works. DNS is broken. Skip to solution 2.
• Both fail, but you have a valid IP address — connectivity beyond the router is broken. Solutions 4 through 8.
• ipconfig shows 169.254.x.x — DHCP failed. Solution 3.
• Everything succeeds but the browser fails — a browser, proxy, or firewall problem, not a network problem.

This test alone identifies the category of fault, and each category has a different fix.

Solution 1: Restart in the Correct Order

Restarting works surprisingly often, but the order matters and almost nobody follows it.

The correct sequence:

1. Power off every device — modem, router, switches, computers.
2. Wait 60 seconds. This is not superstition. It allows capacitors to discharge fully and, on some connections, prompts the provider to release the old session.
3. Power on the modem first. Wait until its lights are stable — usually two to three minutes.
4. Power on the router. Wait for it to fully boot — another one to two minutes.
5. Power on switches, then computers.

Why the order matters: a router that boots before its upstream connection is ready may fail to obtain an address from the provider and will not retry for a long interval. Restarting everything simultaneously is the most common reason a restart "does not work."

Solution 2: Fix DNS

DNS server problems are the single most common cause of this exact symptom, and the easiest to fix.

The signature: you can ping IP addresses, but website names do not resolve. The internet is reachable; your device simply cannot translate names into addresses.

First, clear the local cache:

ipconfig /flushdns

If that does not resolve it, set DNS manually:

1. Open Network Connections and access your adapter's properties.
2. Select Internet Protocol Version 4 and open its properties.
3. Choose "Use the following DNS server addresses."
4. Enter a reliable public resolver — for example 8.8.8.8 with 8.8.4.4, or 1.1.1.1 with 1.0.0.1.
5. Apply, then run ipconfig /flushdns again.

Test immediately:

nslookup google.com 8.8.8.8

If this succeeds while your default DNS fails, you have proven the cause.

A note on why this happens so often: many routers hand out themselves as the DNS server and forward queries upstream. When that forwarding breaks — through a firmware bug, a full cache, or a provider issue — everything appears connected while nothing resolves.

Solution 3: Resolve DHCP Failure

DHCP failure is identified by one unmistakable clue: an IP address starting 169.254.

That address is APIPA. Windows assigns it when it asks for an address and receives no answer.

Try renewal first:

ipconfig /release
ipconfig /renew

If you still receive a 169.254 address, the causes in order of likelihood are:

1. A physical problem — dead cable, bad port, or no link. Check the link lights.
2. DHCP disabled on the router, often after someone changed settings.
3. DHCP pool exhausted. If the pool holds fifty addresses and sixty devices have connected, the last ten receive nothing. Check the router's client list and reduce the lease time if it is full.
4. A second DHCP server on the network, handing out addresses for a different subnet. This happens when someone plugs a spare router into a switch without disabling its DHCP service.

Point four is worth checking carefully in offices. An accidental second DHCP server produces intermittent, seemingly random failures that are very hard to trace.

A temporary workaround while you investigate: assign a static IP address in the correct range, with the router as gateway and a public DNS server. If that restores internet access, DHCP is confirmed as the fault.

Solution 4: Check Whether the Fault Is Your Provider

Before spending an hour on your own equipment, spend two minutes ruling out the obvious.

1. Check your mobile data — is the provider's mobile network working?
2. Look at the modem lights. Every modem has an indicator for the upstream connection. If it is off, flashing, or red, the problem is outside your building.
3. Check the provider's status page or social accounts using mobile data.
4. Ask a neighbour on the same provider.
5. Check whether the account is paid. This is a genuinely common cause and an embarrassing one to discover after two hours of troubleshooting.

If the modem shows no upstream connection, stop troubleshooting. Nothing you configure will help.

Solution 5: Resolve an IP Address Conflict

IP address conflict occurs when two devices hold the same address.

Symptoms:

• Connectivity that works intermittently.
• Windows displaying a conflict warning.
• One device working normally while another fails on the same network.

How it happens: someone assigned a static address inside the DHCP pool range. When DHCP later hands that same address to another device, both break.

To fix it:

ipconfig /release
ipconfig /renew
arp -d *

To prevent recurrence: reserve a block of addresses outside the DHCP pool for static assignments. On most routers this means setting the pool to start at, for example, .50 and keeping .2 to .49 for printers, servers, and access points.

Solution 6: Check the Physical Path

It is still, very often, a cable.

1. Check link lights at both ends. No light means no signal.
2. Reseat every connector. A plug that looks seated can be slightly out.
3. Swap the modem-to-router cable with a known-good one. This specific cable fails often because it is rarely inspected.
4. Check for damage where cables pass under furniture or through doorways.
5. Try a different port on the router.

And confirm the cable is in the correct port. The WAN or Internet port is separate from the numbered LAN ports. A modem connected to a LAN port produces exactly this symptom.

Solution 7: Check MAC Filtering and Access Controls

Many routers include a MAC filter that permits or blocks specific devices.

If one device fails while others work normally, check:

1. MAC address filtering — is your device on a block list, or missing from an allow list?
2. Parental controls or scheduled access — some routers block devices during set hours.
3. Device-specific bandwidth limits.
4. Guest network isolation — a device on the guest network may be intentionally restricted.

Find your MAC address with:

getmac /v

Then compare it against the router's device list.

Solution 8: Check Firewall and VPN Software

The fault is sometimes on the device, not the network.

1. Disable third-party firewall software temporarily and test. Re-enable it immediately afterwards regardless of the result.
2. Disconnect any VPN client. A VPN that disconnects badly can leave routing rules in place that send all traffic to a tunnel that no longer exists.
3. Check for a configured proxy in your system's internet settings. A proxy set for a previous network will break everything on a new one.
4. Check the routing table:

route print

Look for the destination 0.0.0.0 entry. If there are two default routes and the wrong one has priority, traffic is going nowhere useful.

If disconnecting a VPN restores the connection, reset the stack properly:

netsh winsock reset
netsh int ip reset

Restart the computer afterwards.

Solution 9: Update or Reset the Router

Routers fail gradually, in recognisable ways.

Before resetting, check two things:

1. Router uptime. A router that reboots on its own is failing.
2. Temperature. Overheating is the leading cause of a router that works for hours then drops. Move it out of enclosed cabinets, away from other heat sources, and ensure its vents are clear.

Then update the firmware. Many "router needs restarting weekly" problems are memory leaks resolved in a later release.

A factory reset is a last resort. Record your provider credentials, Wi-Fi name, and passphrase before doing it, because everything will be erased and some providers require specific settings to reconnect.

Solution 10: Test With a Second Device

This is diagnostic rather than a fix, and it should honestly be done earlier.

Connect a phone or a second computer:

• If the second device works, the network is fine. The fault is on the original device — adapter, drivers, firewall, or configuration.
• If neither works, the fault is the router, modem, or provider.

One minute of testing eliminates half the possible causes, and it prevents the very common mistake of reconfiguring an entire network to fix one laptop.

The Order to Work Through

Run them in this sequence, not at random:

1. Test a second device — is this one machine or everything?
2. Run the three-command diagnostic — ipconfig, ping, nslookup.
3. Check modem lights and provider status.
4. Restart in the correct order.
5. Fix DNS if names fail but IP addresses work.
6. Fix DHCP if you see a 169.254 address.
7. Check cables and ports.
8. Check MAC filtering, firewall, and VPN.
9. Check router temperature, uptime, and firmware.
10. Factory reset only after everything else.

Change one thing at a time. If you change five settings and it works, you have learned nothing and cannot prevent a recurrence.

Conclusion

The message is not lying to you — it is simply reporting a narrower fact than you assumed. "Connected" describes the link between your device and the router. It says nothing about everything beyond it.

Start with the single most informative test: run ping 8.8.8.8 and nslookup google.com together. If the first succeeds and the second fails, you have found your answer in ten seconds, because DNS is the most common reason a router connected but no internet message appears — and it is also the fastest one to fix.