When Ethernet shows connected but no internet, the problem is usually not the cable alone.
The failure can come from router settings, IP configuration, DNS, driver issues, or a wider ISP outage.
What “Ethernet Connected but No Internet” Means
This status typically means your computer has a physical link to the network adapter and can communicate at the local layer, but it cannot reach the public internet.
In practical terms, your device may be talking to the router, switch, or modem, yet traffic is not making it beyond your local network.
The key to fixing it is to separate the problem into layers: physical connection, local network access, IP addressing, name resolution, and upstream internet service.
That layered approach saves time and avoids random trial-and-error.
Common Causes of Ethernet Showing Connected but No Internet
- Loose or damaged Ethernet cable causing unstable link negotiation.
- Faulty router, modem, or switch that passes local traffic but cannot route to the internet.
- Incorrect IP address assignment from DHCP or a static IP conflict.
- DNS failures that prevent websites from resolving even when the network is live.
- Disabled or outdated network adapter drivers on Windows or macOS.
- MAC address filtering, parental controls, or firewall rules blocking access.
- ISP outage or authentication problem at the modem or ONT.
Start With the Fastest Checks
Before changing settings, confirm whether the outage is local or external.
A few quick checks can eliminate the most common causes.
Check link lights and port status
Look at the Ethernet port on your computer, router, or switch.
A solid or blinking light usually means the physical link is up.
If there is no light, try another cable, another port, or another device to verify the connection.
Restart the network equipment
Power cycle the modem, router, and computer in that order.
Unplug the modem and router for 30 seconds, reconnect the modem first, wait until it fully syncs, then reconnect the router and computer.
This clears temporary faults and renews many ISP sessions.
Test another device on the same cable
If another laptop or desktop gets internet on the same Ethernet cable, the cable and router port are likely fine.
If every device fails, the issue is probably in the router, modem, or ISP connection.
Verify the IP Configuration
A device can appear connected while receiving an unusable IP configuration.
This is one of the most common reasons Ethernet connected but no internet appears on Windows and other operating systems.
Check for a valid IP address
On Windows, open Command Prompt and run ipconfig.
A healthy setup usually shows an IP address in your local subnet, a subnet mask, a default gateway, and DNS servers.
If you see an address like 169.254.x.x, the device did not get a DHCP lease from the router.
On macOS, open Network settings and inspect the Ethernet details.
On Linux, use ip addr and ip route to confirm the interface has a proper address and gateway.
Renew the DHCP lease
If DHCP failed, renew the lease.
On Windows, run:
ipconfig /releaseipconfig /renew
If the address still fails to renew, restart the router or verify that DHCP is enabled in the router configuration.
Remove static IP mistakes
If you manually set an IP address, make sure it matches the correct subnet and does not conflict with another device.
In many homes and small offices, switching back to automatic IP assignment resolves the problem immediately.
Rule Out DNS Problems
Sometimes the internet works, but websites fail because DNS cannot translate names into IP addresses.
In that case, the system may still report connected but no internet, even though raw connectivity exists.
Test by IP address
Try opening a site by IP address or pinging a public IP such as 8.8.8.8.
If that works but a domain name does not, DNS is likely the issue.
Change DNS servers
Switch to a reliable public resolver such as Google Public DNS, Cloudflare DNS, or your ISP’s recommended servers.
Common options include 8.8.8.8, 8.8.4.4, 1.1.1.1, and 1.0.0.1.
Flush the DNS cache
Stale DNS records can cause connection failures even after the network is fixed.
On Windows, run ipconfig /flushdns.
On macOS, use the appropriate DNS flush command for your version.
Then test the connection again.
Inspect Router, Modem, and ISP Status
If your device has a valid IP address but nothing reaches the internet, focus on the upstream equipment.
Many users assume the PC is at fault when the router or modem is actually offline, misconfigured, or partially connected.
Check the modem or ONT indicators
Most modems and fiber ONTs have status lights for power, link, upstream, and internet.
A missing or red internet light often indicates a line problem, provisioning issue, or outage.
Log in to the router
Open the router admin page and check WAN status, DHCP, PPPoE credentials, and DNS settings.
If the WAN IP is blank or private when it should be public, the router may not be getting internet from the modem.
Look for captive portals or authentication failures
Some networks, especially in apartments, hotels, dorms, and offices, require browser-based login or network authentication.
Until you complete that step, Ethernet may appear connected but no internet will work.
Update or Reset the Network Adapter
Driver problems can break internet access even when Windows shows the adapter as connected.
This is especially common after system updates, hardware changes, or sleep/wake cycles.
Update the Ethernet driver
In Device Manager, open the network adapter properties and check for driver updates.
Install the latest driver from the motherboard, laptop, or NIC manufacturer if Windows provides an older generic version.
Disable and re-enable the adapter
Turning the adapter off and back on can clear a stuck state.
This step is quick and often restores connectivity after a transient fault.
Reset network settings
On Windows, a network reset can remove corrupted configuration files and restore defaults.
Use this option carefully if you have custom VPNs, virtual adapters, or static settings, because you may need to reconfigure them afterward.
Check for Security Software and Firewall Interference
VPN clients, endpoint protection tools, and third-party firewalls can block traffic while leaving the physical Ethernet link intact.
If the problem began after installing security software, temporarily disable it for testing.
Also review router-based parental controls, MAC filtering, access control lists, and guest network restrictions.
These features can allow the device to connect locally but deny internet access based on policy.
Use a Simple Isolation Method
A structured isolation method is often the fastest way to find the fault:
- Test a different Ethernet cable.
- Test a different router or switch port.
- Test a second device on the same port and cable.
- Test the original device on a different network.
- Test internet access directly from the modem or ONT if your setup allows it.
Each step narrows the problem to one of four areas: cable, local hardware, device configuration, or ISP service.
When to Suspect a Hardware Failure
If multiple cables, ports, and devices fail consistently, hardware damage is possible.
A failing Ethernet jack, router port, switch port, or network interface card may still show a link light while dropping packets under load.
Watch for repeated disconnects, extremely slow throughput, negotiation stuck at 100 Mbps instead of 1 Gbps, or link lights that flicker unpredictably.
Those are signs the physical layer needs attention.
Practical Fix Order for Ethernet Connected but No Internet
- Restart the modem, router, and PC.
- Swap the Ethernet cable and router port.
- Check the IP address and gateway.
- Renew DHCP and flush DNS.
- Test another device on the same connection.
- Update or reset the Ethernet driver.
- Review router WAN status and ISP alerts.
- Contact the ISP if the modem or ONT cannot reach the internet.
Following that order helps you identify whether the issue is inside your device, inside your network, or outside your home or office.
Once you know the layer that is failing, the fix becomes much faster and more predictable.
