Article not found

Ethernet connected but no internet

A step-by-step guide to fixing an Ethernet connection that shows connected but has no internet access.

Ethernet connected but no internet

Introduction

Seeing an Ethernet connection that says “connected” but still no internet is frustrating. You might expect a wired connection to be stable and fast, yet webpages refuse to load. This problem usually comes down to a local network issue, a router or modem problem, or a device configuration problem. The key is to identify where the connection breaks: your device, the router, or the internet service itself.

Ethernet is often more reliable than Wi‑Fi, so when it fails, the cause is typically something specific. It could be a misconfigured IP address, a damaged cable, or a router that has lost its internet connection. Some issues are quick to fix, while others indicate a larger ISP or hardware problem.

This guide provides a practical troubleshooting path to restore internet access while keeping your network stable.

If you have a managed network at work, note that some networks require authentication or specific VLAN settings. In those environments, “connected” only means the physical link is active; the network may still block internet access until the correct credentials or configurations are applied.

When the issue becomes a recurring concern, focus on when the symptom appears and what changed just before it did. Tracking timing, frequency, and environment helps you avoid random fixes and narrows the likely causes quickly.

What this actually means

Your computer shows a physical link to the router (the Ethernet connection), but it cannot reach the wider internet. That usually means the cable is working but the connection beyond the router is not. It can also indicate DNS issues or IP conflicts that prevent your device from reaching external sites.

The goal is to check each link in the chain: your device, the router, and the internet service.

If your computer shows a “connected, no internet” message but local network devices still work, the issue may be upstream DNS or ISP routing. That distinction can help you avoid unnecessary changes to local settings when the real problem is beyond your network.

Common causes / reasons

DNS issues. Your device cannot resolve website names.
Router offline. The router has lost its connection to the modem or ISP.
IP conflicts. Two devices may be using the same IP address.
Cable problems. A damaged cable can still show a link but fail to transmit data.
Incorrect network settings. Static IP settings may not match your network.
ISP outage. The service may be down in your area.

Step-by-step guidance

Check another device. See if other devices on the network have internet access.
Restart the router and modem. Power cycle both and wait for full reboot.
Swap the Ethernet cable. Use a known good cable to rule out damage.
Renew IP address. Use network settings to release and renew the IP.
Check DNS settings. Switch to a public DNS like 1.1.1.1 or 8.8.8.8.
Disable and re‑enable the adapter. This resets the connection on the device.
Check for IP conflicts. Ensure no static IP is duplicated.
Contact ISP if needed. If no devices have internet, the ISP may be down.

If you use a managed switch, check whether the port is assigned to the correct VLAN. A misconfigured VLAN can show a physical connection while blocking internet access. Testing the same cable on a known good port can quickly confirm whether the switch configuration is involved.

Troubleshooting table: Ethernet no internet

| --- | --- | --- | --- |

How to confirm the fix

After applying a fix, open several different websites and run a speed test. This confirms both DNS resolution and actual data throughput. If only one site fails, the issue may be specific to that service rather than your connection.

You can also run a quick ping to a known IP address and then to a domain name. If the IP ping works but the domain ping fails, DNS is still the likely issue. This simple check can save time when diagnosing repeat failures.

Common mistakes (what NOT to do)

Ignoring the modem. Many problems are upstream of the router.
Assuming Wi‑Fi works means Ethernet should. They can fail independently.
Using old or damaged cables. Link lights do not guarantee good data flow.
Leaving static IP settings. Static settings can break DHCP networks.
Skipping DNS checks. DNS issues can look like full internet failures.

When this cannot be fixed / limitations

If the ISP is down or the modem has failed, local troubleshooting will not restore internet access. Similarly, if the Ethernet port on your device is physically damaged, no software fix will help. In those cases, you may need to use a different device, a USB Ethernet adapter, or contact your ISP for a modem replacement.

Some workplace networks also require device registration or MAC address authentication. If your device is new or recently reset, the network may block internet access until it is approved. In that case, contact your network administrator rather than changing local settings.

When to seek professional help

The problem affects critical data or business continuity.
Symptoms persist after safe, basic troubleshooting.
You suspect electrical damage, physical failure, or warranty-sensitive repairs.

Prevention tips

Use quality Ethernet cables, keep your router firmware updated, and avoid unnecessary network changes. If you use static IPs, document them clearly to prevent conflicts. A simple backup plan—like a USB Ethernet adapter—can also save time if a port fails.

It can also help to label your network gear and cables if you have multiple devices. Knowing which cable goes to the modem versus a switch reduces the chance of accidental miswiring after a move or cleanup. Small organization steps prevent common “connected but offline” mistakes.

Keep router firmware on a stable release track rather than beta builds, and note any ISP maintenance alerts. Avoid stacking networking gear in enclosed spaces, and label cables so replacements are quick during outages.

FAQs (6–8 real questions)

Why does Ethernet show connected but no internet?

The physical link is active, but the router or ISP may be offline.

Should I reset my router?

Restarting is safe; resetting to factory should be a last resort.

Can a bad cable still show a connection?

Yes. The link light can be on even if data transmission is unstable.

Does changing DNS help?

If the issue is DNS, switching to a public DNS often fixes it.

Is this a sign my Ethernet port is failing?

Only if other cables and devices still fail on that port.

Should I call my ISP?

If all devices are offline, contact the ISP after basic checks.

Summary and key takeaways

Treat ethernet connected but no internet as a signal to confirm symptoms and recent changes.
Make one change at a time and verify stability before moving on.
Prioritize data safety and long-term reliability over quick fixes.
Escalate to professional help when risks or uncertainty increase.

Disclaimer

This article provides general troubleshooting guidance and does not replace ISP support or professional network service.

Last updated date

2026-02-13