If router has internet but devices say no internet, start by comparing one working device with one failing device, then check router status, IP address, DNS, VPN or proxy settings, and whether the device is paused or isolated in the router app.
Do a normal restart sequence before deeper changes: modem or fiber box first, router second, affected device last. Save factory reset for the very end.
The connection status is only one clue
When router has internet but devices say no internet shows up, the status message is telling only part of the truth. The router, computer or TV may be connected to one layer of the network while the next layer is still broken. That gap is why this problem feels so annoying: the icon looks confident, the app says connected, and then normal pages or apps refuse to load. The fastest fix is to avoid one giant reset and test the path in pieces. First prove whether the issue affects one device or every device. Then check the local network, address assignment, DNS and the upstream internet side. That order keeps you from replacing equipment that is still doing its job.
This guide is written for the practical home setup: a provider modem or ONT, a router or mesh system, and a mix of phones, laptops, TVs and consoles. The exact menu names change by brand, but the logic stays steady. If the connection works in one place and fails in another, the failed handoff is your clue.
Quick diagnosis table
Try these fixes in order
Work through the checks in this order. Each step is designed to prove one part of the connection before you move to the next.
- 01
Restart in the right order
Step 1 should narrow one part of the path instead of changing everything at once. After you make this check, test a normal website and one app that was failing before. If the result changes, write it down before moving to the next fix.
- 02
Compare one failing and one working device
Step 2 should narrow one part of the path instead of changing everything at once. After you make this check, test a normal website and one app that was failing before. If the result changes, write it down before moving to the next fix.
- 03
Check the router status page or app
Step 3 should narrow one part of the path instead of changing everything at once. After you make this check, test a normal website and one app that was failing before. If the result changes, write it down before moving to the next fix.
- 04
Put IP and DNS back to automatic for one test
Step 4 should narrow one part of the path instead of changing everything at once. After you make this check, test a normal website and one app that was failing before. If the result changes, write it down before moving to the next fix.
- 05
Turn off VPN, proxy or security filtering briefly if allowed
Step 5 should narrow one part of the path instead of changing everything at once. After you make this check, test a normal website and one app that was failing before. If the result changes, write it down before moving to the next fix.
- 06
Check router pauses, guest network and isolation settings
Step 6 should narrow one part of the path instead of changing everything at once. After you make this check, test a normal website and one app that was failing before. If the result changes, write it down before moving to the next fix.
- 07
Update device or adapter software if only one device fails
Step 7 should narrow one part of the path instead of changing everything at once. After you make this check, test a normal website and one app that was failing before. If the result changes, write it down before moving to the next fix.
- 08
Call the provider only when the upstream clues point there
Step 8 should narrow one part of the path instead of changing everything at once. After you make this check, test a normal website and one app that was failing before. If the result changes, write it down before moving to the next fix.
Detailed checks
Start by comparing devices
Use one known-good device as your reference. If that device loads websites on the same network, the whole internet service is probably not down. If every device fails at the same time, the router, modem or provider path deserves attention before you dig into one laptop or TV.
- This comparison sounds basic, but it saves time. Many people reset a router because one device has a stale setting, or reinstall a driver because the modem is actually offline.
Check the local network first
Open the router app or router status page if you can. If local pages load but outside websites do not, the device is reaching the router and failing beyond it. If even the router page will not open, look at Wi-Fi connection, Ethernet link, IP address and access-control settings.
- Local success is not the same as internet success. It only proves the first hop works, and that is still useful.
Look for IP and DNS clues
Most home devices need an IP address from the router and a DNS server that can translate names like netflix.com or microsoft.com. If either piece is missing, the connection can look alive while apps fail. Windows may show no internet, TVs may spin forever, and phones may quietly switch to mobile data.
- Automatic IP and DNS are usually the right starting point. Custom settings are useful only when you know why they were set.
Do a clean restart sequence
Restarting in order matters more than restarting everything at once. Power the modem or fiber box first, wait for it to settle, then restart the router, then restart the affected device. This gives each layer a fresh chance to request and hand out network information.
- Do not factory reset during this step. A normal power restart refreshes the connection without erasing names, passwords or provider settings.
Check blocks, pauses and security settings
Router apps now include device pause buttons, parental controls, private address handling, MAC filtering, guest networks and isolation modes. Any of those can make a device look connected but unable to use the internet.
- If the problem affects only one device, look for that device in the router client list. A blocked or paused device often looks normal on the device itself.
Test with one variable changed
Change one thing at a time: a different cable, a different router port, a different Wi-Fi band, a VPN off test, or a DNS back-to-automatic test. If you change five settings together, you may fix it without knowing why, and the problem becomes harder to prevent next time.
- Good troubleshooting is boring in the best way. One change, one test, one note.
Know when the provider is involved
Provider support is useful when several devices fail, modem lights change, the router cannot get a WAN address, or the outage repeats at the same time. They are less useful when one Windows laptop, one TV app or one Ethernet adapter is the only thing failing.
- Before calling, write down what works, what fails and whether Ethernet works. That short note makes the call much less vague.
Mistakes to avoid
Do not trust one status message by itself. Compare devices and connection types.
Do not change several router settings at the same time. One change at a time makes the cause easier to see.
Do not ignore VPN, proxy, guest network or parental-control settings when only one device fails.
FAQ
Why does router has internet but devices say no internet happen?
It usually happens because one layer of the connection works while another layer fails. The device may reach the router but fail DNS, IP assignment, app servers, VPN routing or the provider side of the link.
That is why the status message can look contradictory. Connected is not the same as fully online.
Should I restart the router first?
A normal restart is fine if several devices are affected, but it should not be the only test. Restart the modem or ONT first, then the router, then the device so the network rebuilds in order.
Avoid a factory reset at the beginning. It creates extra work and often does not solve the actual cause.
How do I know if it is only one device?
Test another phone, laptop or TV on the same network at the same time. If the second device works, the router and provider service are probably alive.
Then focus on saved network settings, VPN, DNS, driver, app cache or a device-specific block in the router app.
Can DNS cause this problem?
Yes. DNS can fail even when the Wi-Fi or Ethernet link is connected. When DNS fails, apps and browsers may not know where to send traffic.
Try automatic DNS first. If that fails, testing a known public DNS can be useful, but only keep it if it clearly improves the problem.
Can a router app say online while devices fail?
Yes. The router app may be checking the router's upstream connection, not whether every client device has a clean route through Wi-Fi, DHCP and DNS.
That difference matters. If the router is online but clients fail, inspect local settings like DHCP, device pauses, guest network isolation and Wi-Fi band behavior.
When should I call support?
Call support when multiple devices fail, modem or ONT lights are abnormal, the router cannot get a WAN address, or the issue repeats after clean restarts.
If one device fails while others work, finish the device-level checks first. Support will usually ask for that comparison anyway.
Is this a sign I need a new router?
Not immediately. Many cases come from settings, firmware, DNS, cabling, one weak device or a provider-side event.
Consider replacement only after the same symptom repeats under light use, firmware is current, placement and cables are fine, and several devices show the same failure.
What should I write down before changing settings?
Write down the exact error, affected devices, modem or router light status, whether Ethernet works and the time it happened. That is enough to spot patterns.
Those notes also help if you need provider support later. A clear symptom log beats a long story told from memory.
Outside references
- TP-Link home network support
Official support reference for checking settings, lights or device-specific troubleshooting.
- ASUS router support
Official support reference for checking settings, lights or device-specific troubleshooting.