If Wi-Fi works on 2.4GHz but not 5GHz on one device, start with one clean comparison: test another device, cable, router port, Wi-Fi band, or direct connection before changing router settings.
Then restart in order, check IP and DNS, inspect router app blocks or firmware, and call the provider only when several devices or modem lights point upstream.
Do not treat every connection problem as the same problem
When Wi-Fi works on 2.4GHz but not 5GHz on one device, it is tempting to treat the whole network as broken. In many homes, though, the clue is narrower than that. One light, one port, one band, one device, or one repeated error can tell you exactly where the connection stopped. The tricky part is that the rest of the network may still look normal. Wi-Fi names can appear, router apps can show online, and devices can say connected while the actual internet path is still failing. That is why the fix should start with comparison, not panic. Compare one working thing with one failing thing, watch the lights or status messages, then change only one variable at a time.
This guide uses a practical home troubleshooting order. You will check the visible symptom first, then the cable or wireless link, then IP and DNS, then firmware or provider involvement. It is slower than mashing reset once, but it gives you a real answer and keeps your saved network settings intact.
Quick diagnosis table
Try these fixes in order
Move through these checks in order. The goal is to prove which layer failed before you spend money or erase settings.
- 01
Record the exact error or light pattern
This step gives you a clearer before-and-after result. Test the failing website, app, light, port, or band again after the change, and write down whether anything improved before moving on.
- 02
Compare with another device or connection type
This step gives you a clearer before-and-after result. Test the failing website, app, light, port, or band again after the change, and write down whether anything improved before moving on.
- 03
Restart modem or fiber box, then router, then device
This step gives you a clearer before-and-after result. Test the failing website, app, light, port, or band again after the change, and write down whether anything improved before moving on.
- 04
Bypass one cable, splitter, wall jack or switch for a test
This step gives you a clearer before-and-after result. Test the failing website, app, light, port, or band again after the change, and write down whether anything improved before moving on.
- 05
Return IP and DNS settings to automatic
This step gives you a clearer before-and-after result. Test the failing website, app, light, port, or band again after the change, and write down whether anything improved before moving on.
- 06
Check router app blocks, paused devices and guest isolation
This step gives you a clearer before-and-after result. Test the failing website, app, light, port, or band again after the change, and write down whether anything improved before moving on.
- 07
Update firmware or adapter drivers when one device keeps failing
This step gives you a clearer before-and-after result. Test the failing website, app, light, port, or band again after the change, and write down whether anything improved before moving on.
- 08
Call provider support when multiple devices or modem lights point upstream
This step gives you a clearer before-and-after result. Test the failing website, app, light, port, or band again after the change, and write down whether anything improved before moving on.
Detailed checks
Use the symptom as a map
The exact wording matters. A blinking modem light, a WAN port with no link, a DNS message, and a 5GHz-only failure are not the same problem. They all stop internet access, but they fail at different layers.
- Write down the wording before changing settings. If the issue returns tomorrow, that note helps you see whether it is the same fault or a new one.
Compare one known-good path
Find one path that works, even if it is not the path you want to use every day. That might be Ethernet instead of Wi-Fi, 2.4GHz instead of 5GHz, another router port, or another device on the same cable.
- A working comparison tells you what not to blame. That is half the battle in home networking.
Restart in a clean order
Power cycling can help, but order matters. Start with the modem, fiber box, or provider gateway. Wait until its main status lights settle, then restart the router, then restart the affected device.
- This sequence gives the upstream equipment time to hand off a fresh address before the router and device ask for one.
Check cables, ports and placement
Loose Ethernet plugs, old coax splitters, warm cabinets, kinked patch cables and hidden wall jacks can all create symptoms that look like software problems. Physical checks are boring, but they are quick and cheap.
- Replace or bypass one cable for a test before buying a modem, router, USB adapter or mesh system.
Reset saved network state carefully
Devices remember old network details. That memory is useful until the router, DNS, password, security mode, or IP range changes. Forgetting the network and joining again can clear a stale profile without wiping the whole router.
- On Windows, a network reset is stronger and should come later. On TVs and phones, start with forgetting the network or clearing the affected app cache.
Use official apps only as clues
Provider and router apps are helpful, but they do not always test the same thing you are seeing. An app may say the modem is online while a device still cannot get DNS or local access.
- Treat app status as one clue, then confirm with a second device, a wired test, or the router status page.
Know when support is worth calling
Support is worth calling when several devices fail, modem lights never settle, the router cannot get a WAN address, or the symptom repeats after a clean restart. Those are upstream clues.
- If one device, one band, or one port fails while everything else works, finish local checks first. That gives support better information if you still need them.
Mistakes to avoid
Do not assume Wi-Fi bars prove internet service is working.
Do not change DNS, security mode and router placement all at once.
Do not replace hardware until you have tested another cable, device or connection path.
FAQ
Why does Wi-Fi works on 2.4GHz but not 5GHz on one device happen?
It happens when one part of the network succeeds but the next part fails. The device may see Wi-Fi, the router may see the modem, or the modem may see partial signal, but the complete path to the internet is not healthy.
That is why the status can feel contradictory. Connected only describes one layer. Online requires the local device, router, DNS and provider side to agree.
Should I reset the router?
Use a normal restart if several devices are affected, but do not factory reset at the beginning. A restart refreshes leases and connections without erasing your Wi-Fi name, password and settings.
Factory reset is a last step after you have checked cables, device settings, DNS, firmware and provider clues. It can create more work than it solves.
How do I know if this is a provider problem?
Look for symptoms that affect the whole home: multiple devices offline, modem lights not settling, provider app showing an outage, or the router unable to get an internet/WAN address.
If the issue affects one device, one Ethernet port, or one Wi-Fi band, it is more likely local. Still write down the times in case the pattern points upstream later.
Can DNS make the internet look disconnected?
Yes. DNS translates website and app names into reachable addresses. If DNS fails, the device may still be connected to the router but unable to load normal sites.
A useful test is whether IP-based checks work while named websites fail. Most users can simply try automatic DNS first, then test a public DNS only if automatic keeps failing.
Can firmware cause this?
Firmware can cause repeat disconnections, port behavior changes, band steering problems and modem registration issues. This is especially possible after a router update or provider-pushed modem update.
Check the router or modem app for updates and release notes. If the problem began right after an update, search the model name with the exact symptom before replacing hardware.
What should I test before buying new equipment?
Test another device, another cable, another router port, a direct connection near the router, automatic DNS, and a clean restart sequence. Those checks cover the most common false alarms.
If the same symptom survives all of those tests and affects normal light-use conditions, then replacement becomes more reasonable.
Why does the problem come and go?
Intermittent problems often come from heat, marginal signal, loose cables, channel changes, DHCP renewals, or a device roaming between bands. They are harder to catch because everything looks fine after the connection returns.
Keep a simple log with time, affected devices and light status. Three notes can reveal a pattern that one memory cannot.
What is the safest first fix?
The safest first fix is comparison: test another device or another connection type before changing settings. Then restart in order if more than one thing is affected.
That gives you useful information without wiping settings, losing passwords or making the network harder to restore.
Outside references
- Intel wireless adapter support
Official support reference for checking equipment status, settings or model-specific troubleshooting.
- Google Nest Wifi help
Official support reference for checking equipment status, settings or model-specific troubleshooting.