If Ethernet works but Wi-Fi has no internet, your modem and provider connection are probably working. Test a Wi-Fi device near the router, restart the router, check whether Wi-Fi radios are enabled, remove guest network isolation, and make sure wireless clients are getting normal IP and DNS settings.
If only one Wi-Fi device fails, forget the network on that device and reconnect before changing router settings for the whole home.
A working cable is a useful clue
When Ethernet works but Wi-Fi has no internet, you already know something important: the internet service is reaching the router or at least reaching a wired part of the network. That means the problem is probably not the monthly plan, the website you are visiting, or a total provider outage. The break is more likely in the wireless side of the router, a guest network, a band steering setting, a device pause rule, DHCP, DNS, or one stubborn saved Wi-Fi profile.
The best move is to compare wired and wireless paths without resetting everything. Keep one wired device online as your reference. Then test Wi-Fi near the router, test a second Wi-Fi device, and check whether the router is handing wireless clients the same kind of local network access that Ethernet clients receive.
Quick diagnosis table
Try these fixes in order
Use Ethernet as proof that the upstream connection works, then narrow the wireless side.
- 01
Confirm Ethernet really has internet
Open several sites on the wired device. If Ethernet is stable, leave it connected as your reference while fixing Wi-Fi.
- 02
Test Wi-Fi beside the router
A nearby test separates weak coverage from a router-wide wireless problem. If nearby Wi-Fi works, the issue is range or interference.
- 03
Restart the router normally
A normal restart can reload the wireless radios and DHCP service without erasing your network name or password.
- 04
Check that Wi-Fi radios are enabled
Some routers let 2.4GHz or 5GHz be disabled separately. Make sure the expected network is actually broadcasting.
- 05
Move devices off guest Wi-Fi
Guest networks can block local access or use separate rules. Test on the main Wi-Fi before changing advanced settings.
- 06
Forget the network on one failing device
A stale saved profile can keep using old security, DNS or IP details. Forget and rejoin the Wi-Fi cleanly.
- 07
Check DHCP and DNS for Wi-Fi clients
If Wi-Fi clients do not get normal local IP addresses, the router may not be handing out addresses correctly on wireless.
Detailed checks
Why the provider is usually later
If Ethernet works through the same router, the provider path is not the first place to spend time. The router has internet; Wi-Fi clients are failing to use it.
- Provider support may still help later, but your first evidence points inside the home network.
Guest networks can mislead you
A guest network can look like normal Wi-Fi while using stricter rules. It may block printers, local devices, or sometimes behave differently from the main SSID.
- For testing, connect to the main network and compare again.
Band steering can hide the failure
Some routers use one Wi-Fi name for 2.4GHz and 5GHz. If one band is unstable, a device may connect but fail as it roams or switches.
- Separating bands temporarily can show whether the issue belongs to one band.
One device means one-device troubleshooting
If every other Wi-Fi device works, do not rebuild the router. The failing device may have a VPN, proxy, driver, private address setting or saved network problem.
- Compare before you change shared settings.
Wireless DHCP matters
Wi-Fi clients need a local IP address just like Ethernet clients. If they connect but get a strange address, they may not be receiving router settings.
- That points to router DHCP, access rules, or a device profile problem.
Check whether the Wi-Fi name changed
After a router swap or factory reset, the old Wi-Fi name may still appear on some devices because they saved a previous profile. The device can try to join the wrong network or a guest version with similar wording.
- Forget the saved network, join the current main Wi-Fi, then compare the result with the wired device again.
Do not ignore router firmware
Wireless radios are controlled by router firmware. A bug can affect Wi-Fi clients while Ethernet keeps working normally.
- If several Wi-Fi devices fail near the router, check for a firmware update before replacing the hardware.
Mistakes to avoid
Do not call the provider before comparing Ethernet and Wi-Fi.
Do not troubleshoot one laptop as if every wireless device failed.
Do not leave devices on guest Wi-Fi while testing.
FAQ
Why does Ethernet work but Wi-Fi has no internet?
Because the wired path and wireless path are separate. Your router may have internet on its WAN side and still fail to serve wireless clients correctly.
The usual causes are disabled radios, guest network rules, DHCP problems, DNS problems, band steering, router firmware or one device's saved Wi-Fi profile.
Does this mean my internet provider is fine?
Usually, yes, at least for the first round of troubleshooting. If a wired device can browse normally through the same router, the provider connection is reaching your home.
Provider support becomes more relevant if Ethernet later fails too, modem lights change, or the router loses its internet/WAN address.
Should I restart the modem too?
If Ethernet is working, start with the router. Restarting the modem is not harmful, but it may not target the wireless-only problem.
If you do restart both, power the modem first, wait for it to settle, then restart the router and Wi-Fi device.
Can guest Wi-Fi cause no internet?
Yes. Guest Wi-Fi can run separate rules, isolation, time limits or access controls. Some routers also treat guest clients differently from main-network clients.
For diagnosis, use the main Wi-Fi network. Once the connection works there, you can decide whether guest settings need adjustment.
Why does only one Wi-Fi device fail?
That points away from the router as a whole. The device may have a stale profile, VPN, proxy, private address setting, adapter driver problem or blocked status in the router app.
Forget the network and reconnect before changing shared router settings.
Can DNS affect only Wi-Fi?
It can if wireless clients are receiving different DNS settings or if one device has custom DNS. DNS can make Wi-Fi look connected while websites fail.
Put DNS back to automatic for a test, then try a trusted public DNS only if automatic keeps failing.
If Ethernet and Wi-Fi use the same router DNS but only Wi-Fi fails, DNS may be a symptom rather than the root cause. Check DHCP, guest isolation and wireless access rules too.
When should I replace the router?
Replace it only after you confirm Wi-Fi fails across several devices, near the router, after a clean restart and firmware check.
If Ethernet remains stable and Wi-Fi keeps failing under light use, the wireless radio or firmware may be aging or unstable.
Is Ethernet a good workaround?
Yes. Ethernet is a useful temporary workaround because it avoids the wireless problem completely.
It also gives you a stable connection while you test Wi-Fi radios, placement and device profiles.
For a desktop, TV or console that rarely moves, keeping Ethernet may be better than forcing a weak wireless connection to behave.
Outside references
- Microsoft network connection help
Official Windows network troubleshooting guidance.
- NETGEAR router support
Router-specific support for Wi-Fi radio and firmware checks.