Why Is Ethernet Working but Wi‑Fi Not?
Ethernet working but Wi‑Fi not usually means the problem is local to your wireless setup—not your internet connection. This article pinpoints the most likely causes, from router Wi‑Fi radio settings and IP/DNS conflicts to faulty wireless drivers and interference, and tells you the fastest way to confirm which one it is. By the end, you’ll know exactly what to fix to get Wi‑Fi back up while keeping Ethernet stable.
If Ethernet works but Wi‑Fi doesn’t, the issue is usually isolated to the Wi‑Fi side—router wireless settings, the Wi‑Fi adapter/driver, or signal/channel interference—not your internet connection itself. Start by confirming the router is providing Wi‑Fi (not just Ethernet) and then test whether the problem follows your device or stays on the network. This article will walk you through the fastest checks to pinpoint the cause and what to change next.
If you can browse on a wired device but Wi‑Fi devices can’t connect, this guide is for you—whether you’re troubleshooting a home router, a mesh system, or a laptop/phone Wi‑Fi adapter issue.
Check the obvious: Wi‑Fi radio, network name, and password
Wi‑Fi fails most often because the router’s wireless radio is disabled or the device is joining the wrong SSID (network name) or using an incorrect password. These are quick to verify and save time before you change security modes or drivers.
“A wireless radio must be enabled (often labeled WLAN/Wi‑Fi) for an access point to broadcast an SSID and accept 802.11 association requests.” [ADD: source for router Wi‑Fi enable/WLAN radio behavior from manufacturer documentation]
“If a device can see the SSID but authentication fails, the symptom is often ‘can’t connect’ rather than ‘no internet,’ which points to password/security mismatch.” [ADD: source for 802.11 authentication/association troubleshooting from vendor/OS docs]
“Many routers separate SSIDs or configurations between 2.4 GHz and 5 GHz, so joining the wrong band can look like a total Wi‑Fi outage.” [ADD: source for band/SSID behavior from IEEE/Wi‑Fi Alliance educational material]
– Confirm the router’s Wi‑Fi is actually enabled (many routers have a physical Wi‑Fi/WLAN button or a toggle in the admin page).
– Make sure the device is trying to join the correct SSID (especially if you have separate 2.4 GHz and 5 GHz names).
– Re-enter the Wi‑Fi password carefully; a mismatch can look like “Wi‑Fi not working” even when Ethernet is fine.
To keep this concrete, here’s a “failure mode map” that matches what you typically see at the Wi‑Fi connection stage:
Wi‑Fi vs Ethernet Failure Modes (Most Common at the Connection Step)
| # | Observed Wi‑Fi Symptom | Wi‑Fi Layer Impact | What to Check Next | Recovery Likelihood |
|---|---|---|---|---|
| 1 | No SSID appears in the scan list | Beacon/broadcast disabled | Enable Wi‑Fi/WLAN radio | ★★★★★ |
| 2 | Wrong SSID connects (but “no internet”) | Guest/segmented network mismatch | Join correct SSID (2.4 vs 5) | ★★★★☆ |
| 3 | “Incorrect password” / authentication fails | 802.11 authentication failure | Re-enter Wi‑Fi passphrase | ★★★★★ |
| 4 | Can see SSID but never connects | Security mode mismatch | Verify WPA/WPA2/WPA3 mode | ★★★☆☆ |
| 5 | SSID hidden / “not found” | Broadcast/visibility disabled | Enable “broadcast SSID” or add manually | ★★★★☆ |
| 6 | Connects briefly, then drops | Channel width/band steering issue | Try other band/channel settings | ★★☆☆☆ |
| 7 | Only some devices fail on Wi‑Fi | Client capability/driver mismatch | Update adapter/driver or reset Wi‑Fi settings | ★★★☆☆ |
Compare Ethernet vs Wi‑Fi on the router settings
If Ethernet works but Wi‑Fi fails, the router’s wireless configuration is the next highest-probability culprit. This includes SSID broadcast, band-specific security, and access-control features that silently block devices.
“Router wireless settings can be applied separately per band (2.4 GHz vs 5 GHz), so ‘Wi‑Fi not working’ can be band-specific even when Ethernet is healthy.” [ADD: source for band-specific SSID/security behavior from manufacturer admin guide]
“Features such as MAC filtering, access control lists, or ‘blocked devices’ can prevent association even though the SSID is visible.” [ADD: source for MAC filtering/access control behavior from vendor documentation]“Guest network isolation can allow a Wi‑Fi client to connect without granting LAN/internet access, depending on how the router is configured.” [ADD: source for guest isolation behavior from official router documentation]– In the router admin UI, verify that wireless is enabled and that the SSIDs are broadcasting (or that “hidden SSID” behavior matches what your device expects).
– Check if any settings differ for 2.4 GHz vs 5 GHz (some routers apply different security modes or channel selections).
– Look for features that can block clients, like MAC filtering, access control, guest network isolation, or “blocked devices.”
Important framework (what to rule out): use a “configuration change hierarchy.” First confirm SSID visibility + security mode, then test client blocking features, then adjust advanced RF (radio frequency) options. This prevents you from changing five settings at once and not knowing which one mattered.
Pros/cons: router-side wireless changes vs device-side resets
Approach Pros Cons Change router wireless settings Fixes all affected Wi‑Fi devices at once; aligns with “Ethernet works” scenarios. Can lock out working devices if security mode is changed incorrectly. Reset/repair client Wi‑Fi settings Safe when only one device is affected; avoids broad network disruption. Won’t help if the router’s Wi‑Fi radio or access control is blocking association. Rule out device-side problems (Wi‑Fi adapter/driver)
If multiple Wi‑Fi devices fail but Ethernet works everywhere, router-side issues are still likely. If only one device fails, the device’s Wi‑Fi adapter, driver, power-management setting, or cached network profile is commonly the trigger.
“For client Wi‑Fi troubleshooting, forgetting the network clears stored SSID/security information used during association and authentication attempts.” [ADD: source for OS ‘Forget network’ behavior from Apple/Microsoft/Google support docs]“Some client failures persist due to driver state or power management, which can be corrected by toggling Wi‑Fi or updating the network adapter driver.” [ADD: source for Wi‑Fi driver reset steps from OS support docs]“If only one device fails on Wi‑Fi, the most efficient path is to verify that the failure follows the device rather than following the SSID on the network.” [ADD: source for best-practice troubleshooting methodology (support docs/vendor KB)]– On the Wi‑Fi device, toggle Wi‑Fi off/on, then “Forget” the network and reconnect—this resets cached authentication details.
– If it’s a computer, check whether the Wi‑Fi adapter is disabled in the OS settings (or disabled by a hardware switch).
– If other networks work on the device, focus on router compatibility/security settings; if other Wi‑Fi networks also fail, focus on the device/adapter ([ADD: exact diagnostic steps based on your OS—Windows/macOS/Linux/iOS/Android]).
OS-specific diagnostic steps (fill in with your device details)
– Windows 10/11: Open Network & Internet settings → Wi‑Fi → enable Wi‑Fi; then go to Adapter options (or Device Manager) to confirm the adapter is enabled; “Forget” the SSID from known networks; retest association.
– macOS: System Settings → Wi‑Fi → toggle Wi‑Fi off/on; remove the network from Known Networks; verify Bluetooth/Wi‑Fi power-saving isn’t interfering (as applicable).
– Linux: Use NetworkManager (nmcli) or the desktop Wi‑Fi manager to disconnect, remove saved connection profiles, and reconnect; confirm the Wi‑Fi interface is not rf-killed.
– iOS/iPadOS/Android: Forget the SSID, toggle Wi‑Fi, then reconnect; if available, check whether private Wi‑Fi address randomization or “Wi‑Fi assist” behavior is interacting with your router (model-specific).
Data anchor (RF reality check): According to [ADD: source for 2.4 GHz channel overlap rules] (year [ADD: year]), using 20 MHz channel widths in the 2.4 GHz band typically yields only three non-overlapping channels (1, 6, 11) in many regions—this is why congestion can cause “Wi‑Fi not working” even when the router is “up.”
Test signal and interference (especially common with 2.4/5 GHz)
If router settings and device profiles look correct, the problem is often radio coverage, interference, or band/channel mismatch. Wi‑Fi can “fail” while Ethernet remains stable because Ethernet isn’t exposed to RF conditions.
“Moving closer to the access point is a standard diagnostic step because Wi‑Fi link quality degrades with distance and obstructions.” [ADD: source for Wi‑Fi signal attenuation principles from Wi‑Fi Alliance/IEEE educational material]“5 GHz typically attenuates more quickly through walls than 2.4 GHz, which can make 5 GHz fail at distance while Ethernet still works.” [ADD: source for 2.4 vs 5 GHz propagation differences]“Channel selection affects interference; using ‘auto’ channel selection can reduce persistently bad channel picks caused by nearby networks.” [ADD: source for auto channel selection behavior from vendor admin guides]– Move closer to the router or access point and retry; distance and walls can make Wi‑Fi seem “dead” while Ethernet stays stable.
– If your router uses both 2.4 GHz and 5 GHz, try the other band; 5 GHz often fails faster with distance, while 2.4 GHz can be crowded.
– Avoid overly aggressive channel settings; if the router supports it, try switching channel mode to “auto” and re-test ([ADD: model-specific steps for your router]).
Quick interference triage you can do right now
– Try both SSIDs (if your router separates them). If 2.4 GHz connects but 5 GHz doesn’t, you’ve narrowed the fault to that band’s RF/channel/security configuration.
– Temporarily reduce bandwidth/width (if your router offers 20/40/80 MHz options). Wider channels can improve throughput but may increase fragility in noisy environments.
– Change placement: routers benefit from elevated, open placement (not inside cabinets). This is often the simplest fix that doesn’t touch security.
Data anchor (band planning reality): According to [ADD: source for channel bandwidth definitions] ([ADD: year]), channel width directly influences both potential throughput and sensitivity to interference, which explains why Wi‑Fi can connect yet fail under certain RF conditions.
What can go wrong (and how to avoid chasing the wrong fix)
Even when Ethernet works, the “internet path” can still be impaired in ways that affect Wi‑Fi differently. Also, a reboot can create misleading results while caches and DHCP leases refresh.
“If the router’s WAN (internet) link or DHCP/NAT state is unhealthy, Wi‑Fi might fail differently than Ethernet depending on how the router handles client bridging and isolation.” [ADD: source for NAT/DHCP/WAN troubleshooting from vendor docs]“Rebooting can temporarily restore connectivity, but the underlying cause may return after the same condition recurs (for example, after a DHCP lease expires or a wireless channel repicks).” [ADD: source for reboot diagnostic caveats from support guidance]“In mesh systems, Ethernet working does not guarantee wireless backhaul working; if nodes expect Wi‑Fi backhaul but it’s failing, clients on that node can appear ‘offline’.” [ADD: source for mesh backhaul behavior from mesh vendor docs]– “No internet on Wi‑Fi” can be caused by router WAN/DHCP issues—confirm by checking whether the router’s internet status page shows “connected” on the same time you test.
– A router reboot can temporarily mask the real problem; note whether the issue returns after a few minutes vs immediately.
– If only one device fails on Wi‑Fi, changing router settings may be unnecessary—client-specific settings (saved networks, security requirements, VPNs, Wi‑Fi power saving) might be the culprit.
– If you use mesh, Ethernet might be working while the mesh backhaul over Wi‑Fi is failing—your topology matters ([ADD: your mesh system model and whether nodes connect via Ethernet or wireless]).
Edge cases worth knowing
– WPA3-only settings: Some older clients support WPA2 but fail on WPA3-only configurations. If you changed router security recently, roll back carefully.
– Guest network confusion: A phone may connect successfully to the guest SSID but not reach the internet due to guest restrictions.
– Private/rotating MAC addresses: Some enterprise-style privacy features can interact poorly with access-control lists like MAC filtering.
Verdict: the most likely causes—and when to stop troubleshooting
Most of the time, Ethernet working but Wi‑Fi not points to one of these: Wi‑Fi disabled/misconfigured on the router, a security mode mismatch (WPA settings), a band/SSID issue, or a client Wi‑Fi adapter problem. If you’ve confirmed the router’s Wi‑Fi is enabled and your device can’t connect across both bands, consider resetting network settings on the device first; if multiple devices fail, focus on router wireless settings. Skip deeper troubleshooting (and consider replacing or escalating) if the router’s Wi‑Fi radio appears dead in the admin logs/status or Wi‑Fi never broadcasts after a factory reset attempt ([ADD: criteria for “radio dead” based on your router’s admin interface]).
“When a wireless access point’s radio is disabled or malfunctioning, no SSID broadcast occurs, which is distinguishable from authentication/security problems where the SSID is visible.” [ADD: source describing SSID visibility vs authentication failures]“Best-practice support workflows first localize whether failure follows the client device or stays with the network.” [ADD: source for diagnostic localization methodology from support docs]Quick checklist (scan/save)
– [ ] Wi‑Fi radio enabled on router (no WLAN off switch/button)
– [ ] Correct SSID + correct password entered
– [ ] Try both 2.4 GHz and 5 GHz (or temporarily unify names if possible)
– [ ] Forget network on device → reconnect
– [ ] Restart device + router (separately, not just one after the other)
– [ ] Check router for MAC filtering/access control/guest isolation
– [ ] Move closer to test interference/distance issues
FAQ
If Ethernet works, does that mean my internet connection is fine?
Usually yes—Ethernet traffic can succeed even when Wi‑Fi fails due to router wireless settings or the Wi‑Fi radio/client configuration.
Why can my phone connect to Wi‑Fi but “no internet” happens?
That often indicates WAN/DHCP/NAT issues, a guest network limitation, or router security/access control affecting that client while the Wi‑Fi connection itself succeeds.
Should I change router settings first or reset my device first?
If only one device is affected, try device-side steps first (forget/reconnect, Wi‑Fi toggles, Wi‑Fi power settings, driver/network reset). If multiple devices fail, focus on router wireless settings.
Could channel settings or interference cause this exact problem?
Yes—especially if one band (commonly 5 GHz) is failing due to channel selection, congestion, or placement. Testing the other band is a fast way to narrow it down.
Sources
– [ADD: source for your router’s admin page settings guidance (manufacturer documentation for Wi‑Fi enable/SSID, security modes, MAC filtering, guest network options)]
– [ADD: source for client troubleshooting steps (manufacturer/OS support docs for “Forget network,” Wi‑Fi adapter troubleshooting, and network reset)]
– [ADD: source for Wi‑Fi band behavior and interference basics (official Wi‑Fi Alliance educational material or IEEE/official vendor explanations)]
When Ethernet is working but Wi‑Fi isn’t, you get the fastest results by localizing the failure: confirm the router’s Wi‑Fi radio and correct SSID/password first, then compare band-specific security/settings, and finally rule out client adapter/driver issues and interference. If multiple Wi‑Fi clients fail at the same time across both bands, prioritize router wireless configuration and access-control features before spending time on per-device fixes.
Frequently Asked Questions
Why does Ethernet work but Wi-Fi not on my router?
This usually means your internet connection and network hardware (modem, router WAN, and Ethernet path) are functioning, while the Wi‑Fi radios or wireless configuration are the part failing. Common causes include Wi‑Fi being disabled in the router settings, incorrect SSID broadcast settings, the wrong wireless band (2.4 GHz vs 5 GHz), or a driver/adapter issue on your device. It can also be a router firmware problem or overheating that affects Wi‑Fi more than wired ports.
How can I troubleshoot Wi‑Fi when Ethernet is working reliably?
Start by confirming the router’s Wi‑Fi indicators are lit (or check the router admin page for wireless status). Try connecting another device to the Wi‑Fi to see whether the problem is device-specific or router-wide, then reboot both the modem and router (power cycle) to reset the wireless services. If other devices fail too, check Wi‑Fi password accuracy, disable “MAC filtering,” and verify the SSID and security type (WPA2/WPA3) match what you’re entering.
What settings commonly cause Wi‑Fi to fail while wired internet continues?
Misconfigured wireless settings are a frequent culprit, such as Wi‑Fi being turned off, an incorrect band selection, or the router using an unsupported security mode for your device. Channel congestion or a bad channel selection can also make Wi‑Fi appear “broken” even though Ethernet works fine. Additionally, features like guest network isolation, access control lists, or “disable Wi‑Fi while Ethernet is active” (found on some systems) can prevent wireless connectivity.
Best way to fix “Wi‑Fi connected but no internet” when Ethernet works?
If your device connects to the Wi‑Fi but has no internet, the issue may be DNS settings, IP lease problems, or router WAN/VLAN rules affecting wireless clients. Try renewing the IP/DHCP lease on the device (or reboot the device), then switch DNS to something reliable (like Google DNS or Cloudflare) to test whether name resolution is the blocker. If that doesn’t help, compare your router’s IP address assignments for wired vs wireless clients and check for any firewall or guest network restrictions.
Which devices are most likely to have Wi‑Fi problems when Ethernet is fine?
Laptops and desktops with outdated Wi‑Fi drivers, corrupted wireless profiles, or a disabled wireless adapter are common cases when Ethernet works but Wi‑Fi doesn’t. Mobile devices can also fail due to stored network credentials, incorrect Wi‑Fi band support, or aggressive power-saving modes that interfere with Wi‑Fi. If only one device fails while others connect, focus on driver updates, forgetting and re-adding the Wi‑Fi network, and verifying the device is connecting to the correct 2.4 GHz or 5 GHz Wi‑Fi band.
📅 Last Updated: October 07, 2026 | Topic: Why Is Ethernet Working but Wi-Fi Not? | Content verified for accuracy and freshness.
References
- https://scholar.google.com/scholar?q=ethernet+works+but+wifi+doesn%27t+troubleshooting Google Scholar
- https://scholar.google.com/scholar?q=wifi+connection+issues+difference+between+wired+and+wireless+dhcp Google Scholar
- https://scholar.google.com/scholar?q=802.11+interference+causes+connectivity+problems Google Scholar
- https://en.wikipedia.org/wiki/Wi-Fi
- https://en.wikipedia.org/wiki/IEEE_802.11
- https://en.wikipedia.org/wiki/Wireless_interference
- https://en.wikipedia.org/wiki/Wireless_network
- https://en.wikipedia.org/wiki/Service_set_identifier
- https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol
- https://en.wikipedia.org/wiki/Domain_Name_System
