Ethernet Works but Wi-Fi Has No Internet? Fixes

Why Ethernet keeps working while Wi-Fi fails

Start with the good news: your internet connection is alive. When a device plugged into the router with an Ethernet cable can browse, the router is reaching its ISP and routing traffic correctly. The router is also passing data to wired clients even though some wireless clients are failing. That points away from the WAN port or modem and toward the Wi-Fi side of the network.

Wi-Fi is a separate delivery path. The IEEE 802.11 standard defines the medium access control and physical layer specifications for wireless connectivity, while Ethernet uses wired rules. A client must associate with the router, complete any security checks, and receive an IP address before it can use the same internet gateway that wired devices use. If that wireless path fails at any step, you see this mixed pattern. Review what a router does before changing settings.

Identify the exact failure pattern

Check a second Wi-Fi device before changing router settings. If every wireless device fails while every wired device works, focus on the router's wireless network, DHCP pool, firewall, or DNS. If only one device fails, the router may be fine and the problem is in that client's settings. Use how to troubleshoot no internet as a starting point.

Also separate cannot join Wi-Fi from joined but no internet. A device that shows a connected Wi-Fi icon but cannot open sites usually has an addressing, DNS, or firewall issue. A device that will not join at all is dealing with association, security mode, or range. These two situations need different fixes. See one device will not connect.

• All Wi-Fi clients fail: check router SSID settings, DHCP for wireless clients, DNS, and firewall.
• Only one client fails: check that client's saved network profile, IP settings, DNS, VPN, and security software.
• Wi-Fi joins but browsers time out: start with DNS and firewall, not the modem.

DNS settings that break Wi-Fi clients

DNS is one of the first places to look. A Wi-Fi client can be connected to the router and still fail to open websites if it is using a DNS server address that no longer works or that belongs to an old network. Wired clients may still be fine because their adapter settings or DHCP lease are different. Review DNS on a router to see where the addresses come from.

On the router, check the DNS values that DHCP passes to clients. On the failing device, set the Wi-Fi adapter to obtain DNS automatically, forget the network, then reconnect. If a VPN client or security program is installed, it may override DNS only on that device, so pause it to test and rule out DNS as the cause.

Firewall, guest networks, and wireless isolation

Many routers can apply different firewall rules to wired and wireless clients. Guest networks are commonly isolated from the main LAN, and some configurations block or limit internet access for the guest SSID. If your Wi-Fi devices joined a guest network or a separate SSID, the router may be treating them as untrusted even though Ethernet devices are on the main LAN. Learn more in guest network basics.

Open the router's firewall or access control pages and confirm the main wireless SSID is allowed to reach the internet. Check for wireless isolation, AP isolation, or client isolation settings that block traffic between wireless clients and the router. A setting that only affects Wi-Fi can produce exactly this symptom. Keep router security basics in mind while reviewing these rules, and remember that NIST develops cybersecurity standards, guidelines, and best practices for securing networks and devices.

Security mode also matters. Wi-Fi Alliance states that WPA3 is mandatory for Wi-Fi CERTIFIED devices and that WPA3 networks require Protected Management Frames. A very old client may connect poorly or fail during the security handshake. If this is happening, use a transition mode that supports both WPA2 and WPA3, and check the client's Wi-Fi driver. See WPA3 explained for the details.

Client-side settings that affect only Wi-Fi

Wireless adapters carry more configuration baggage than Ethernet ports. A saved profile from another location can have the wrong security type, a static IP address, or an outdated DNS server. If the client has a static IP with the wrong gateway or subnet, it can join Wi-Fi and yet have no route to the internet. Compare DHCP reservation versus static IP to understand what the client should be using.

On the failing device, forget the network, confirm the adapter is set to receive both IP and DNS automatically, and rejoin. Clear any captive-portal expectation if the client previously used hotel or public Wi-Fi. Then check the router's device list to confirm the client received an address and is not blocked by MAC filtering or a device limit.

Keep the router or replace it

If the fixes above restore Wi-Fi, the existing router is fine. If Wi-Fi remains broken for several devices after checking DNS, firewall, and client settings, the wireless hardware or firmware may be unreliable. You can still use the router for wired connections, but the Wi-Fi side is what needs replacing. Start with when to upgrade your router to decide whether a full swap makes sense.

When choosing a replacement, focus on wireless capabilities. Newer generations such as Wi-Fi 6 and Wi-Fi 7 add features for capacity, efficiency, and security, and a mesh system can correct coverage or handoff problems that look like Wi-Fi failures. Look at the Wi-Fi 6 routers guide, the Wi-Fi 7 routers guide, or mesh systems if the problem spans more than one room.

What to pick for your use

Questions

Why do Ethernet devices have internet while Wi-Fi devices do not?

Because the internet connection and router WAN are working. The break is between the Wi-Fi clients and the router: association, DHCP, DNS, firewall, or client settings. Check all Wi-Fi devices together before changing router settings.

Can DNS affect only Wi-Fi clients?

Yes. If a Wi-Fi client has a stale DNS address or a VPN overrides DNS, it can connect to the router but fail to resolve site names. Wired clients may use a different adapter configuration. Set DNS to automatic on the Wi-Fi adapter and check the router's DHCP settings.

Should I factory reset my router when wired works but Wi-Fi has no internet?

No. A factory reset is disruptive and may erase settings that wired clients need. First save or note the current configuration, then try rebooting the router, updating firmware, and checking Wi-Fi security, DHCP, DNS, and firewall settings.

Can the Wi-Fi security mode stop clients from getting internet?

Security mode can prevent older clients from associating at all. Wi-Fi Alliance says WPA3 is mandatory for Wi-Fi CERTIFIED devices and WPA3 networks require Protected Management Frames. If a client fails during the security handshake, use WPA2/WPA3 transition mode or update the client.

What if only one Wi-Fi device has no internet?

Focus on that device. Forget the Wi-Fi network, verify the adapter obtains an IP address and DNS automatically, and disable any VPN or security software temporarily. Also check the router's device list for MAC filtering or DHCP failures.

Should I replace the router if Wi-Fi stays broken?

If all Wi-Fi clients fail after checking DNS, firewall, and client settings, the wireless side may be failing. You can keep the router for wired use but add or replace it with a router, access point, or mesh system that matches your coverage needs.