Wondering how to know if Ethernet is working? In minutes, you can confirm whether your cable, port, and link are actually live using quick, reliable checks like link lights, link speed, and basic connectivity tests. If those signals don’t match, you’ll know fast whether the problem is the physical connection or your network settings.
Ethernet is working when your network adapter shows a Link/active Ethernet connection and your device can reach your router (gateway) or the internet. In this guide, you’ll learn the fastest visual checks, then how to confirm the connection with IP settings and a simple ping test. If you’re seeing “No internet,” “Unidentified network,” or the Ethernet icon looks connected but nothing loads, this is for you. It also helps if you just moved cables, swapped ports, or updated network settings.
If Ethernet is working, your device should show an “Ethernet/Link” connection (usually with a Link light) and you should be able to reach your router (gateway) or the internet. In this guide, you’ll learn the fastest visual checks, then how to confirm the connection with IP settings and a simple ping test.
If you’re seeing “No internet,” “Unidentified network,” or the Ethernet icon looks connected but nothing loads, this is for you. It also helps if you just moved cables, swapped ports, or updated network settings.
Quick checks you can do in under 2 minutes
If Ethernet is healthy, you should see link detection immediately and be able to reach at least your router in a minute or two. Start by confirming the physical layer (cable + port) because it’s the most common cause of “connected but no internet,” especially after recent moves or swaps.
A visible “Link” indicator generally means the Ethernet port detected a physical connection and completed basic link establishment; when Link is off, the problem is usually cabling, the port, or the NIC.
– Make sure the Ethernet cable is fully seated on both ends (PC and router/switch) and that you used the correct port. A half-seated plug can look “mostly connected” but still fail auto-negotiation.
– Look for an activity/link indicator on your Ethernet port (adapter, switch, or router). Activity (often blinking) indicates the interface is sending/receiving frames.
– If possible, reboot the modem/router once after reseating the cable to clear stuck network states. Rebooting clears DHCP leases and WAN-side sessions that can otherwise stay “stuck” after a physical change.
In practice, I’ve seen Ethernet “mystery failures” resolve immediately after reseating both ends and rebooting the router once—however, . This is consistent with how DHCP and link negotiation behave in real deployments, including small offices where someone changes a patch cord and the switch port stays configured for a different VLAN.
If Ethernet link is working, your device should be able to reach the router’s LAN interface; if you can’t reach the gateway, focus on link/IP/DHCP before assuming an internet outage.
Check link lights and port behavior
If Ethernet is working physically, the port should show a Link light (or equivalent software status) and often an activity blink when you test connectivity. If those indicators don’t match what you’re seeing on your device, treat it as a strong signal that the physical or negotiation layer is failing.
According to IEEE 802.3, twisted-pair Ethernet uses link establishment and auto-negotiation mechanisms so endpoints can agree on speed/duplex; when negotiation fails, Link indicators often remain off or speed drops.
What Link vs Activity usually means
– Link (connection) light: usually indicates the physical connection is detected. If it’s off, the cable/port/adapter may not be negotiating.
– Activity light (blinking): usually indicates traffic. If it never blinks while you’re browsing or pinging, something is wrong above the physical layer—or you aren’t actually producing traffic.
In my day-to-day troubleshooting, the fastest “separation test” is this: I make sure a Link light is on first, then I generate traffic (open a webpage or run a ping). If Link is on but there’s no activity, I focus on IP configuration next, because the adapter can be up while the IP stack isn’t able to send usable frames.
When to swap ports and cables
If your device shows an Ethernet adapter but the router/switch port has no link light:
– try a different router/switch port (rule out a single dead switch port),
– try a known-good Ethernet cable (rule out damaged cable pairs),
– check whether the NIC is disabled in software (Windows/macOS/Linux can silently disable interfaces).
If you see “Link” but your negotiated speed is unexpectedly low (for example, 10 Mbps instead of 100/1000/2.5G), it often points to cable quality or damaged pairs causing the link to downgrade.
Common Copper Ethernet Link Rates vs Typical Cable Limits
| # | Negotiated link speed | Common Ethernet mode | Typical max copper length | Cable category commonly used | What you learn fast | Quick isolation value |
|---|---|---|---|---|---|---|
| 1 | 10 Mbps | 10BASE-T | 100 m | Cat 3 (often) | Cable/pairs likely downgraded or under-capable | ★ ★ ★ ★ ★ |
| 2 | 100 Mbps | 100BASE-TX | 100 m | Cat 5 / Cat 5e | Speed downgrade suggests cable quality issues | ★ ★ ★ ★ ☆ |
| 3 | 1 Gbps | 1000BASE-T | 100 m | Cat 5e (common) | Common “healthy” outcome for home/office LAN | ★ ★ ★ ★ ☆ |
| 4 | 2.5 Gbps | 2.5GBASE-T | 100 m | Cat 5e | Indicates good pairing and capable NIC/switch | ★ ★ ★ ★ ★ |
| 5 | 5 Gbps | 5GBASE-T | 100 m | Cat 5e | Shows link is stable and negotiation succeeded | ★ ★ ★ ★ ★ |
| 6 | 10 Gbps | 10GBASE-T | 100 m | Cat 6a | Cable category usually becomes the limiting factor | ★ ★ ★ ★ ☆ |
| 7 | 1 Gbps (often) | 1000BASE-T | 100 m | Cat 6 | Still “healthy,” but Cat 6 limits differ from Cat 6a for 10G | ★ ★ ★ ☆ ☆ |
Verify your Ethernet IP settings (Windows/macOS/Linux)
If Ethernet is physically connected but internet doesn’t work, the most common next issue is IP configuration—especially DHCP (dynamic addressing). Confirm that your Ethernet adapter has a real IPv4 address and a default gateway so your device knows where to send traffic.
According to RFC 3927, if DHCP fails on many systems, clients use an IPv4 link-local address in the 169.254.0.0/16 range (year: 2005).
What to look for in IPv4 details
On Windows/macOS/Linux, you’re looking for three practical indicators on the Ethernet adapter:
1. IPv4 address exists (and is not link-local 169.254.x.x unless you expect it).
2. Default gateway (router LAN IP) is present.
3. Subnet mask/prefix matches your router’s LAN subnet.
According to IEEE 802.3ab, 1000BASE-T (Gigabit Ethernet over copper) is designed for up to 100 meters per link segment (year: 1999) and link failures often show up as missing or negotiated link behavior rather than “mystery browsing stalls.” IEEE 802.3ab
According to RFC 3927, link-local addressing uses 169.254.0.0/16 when no DHCP response is available (year: 2005). RFC 3927
According to IEEE 802.3u, 100BASE-TX is designed for twisted-pair copper segments up to 100 meters (year: 1995). IEEE 802.3u
As of 2026, these fundamentals still drive most “Unidentified network” cases in consumer and SMB LANs: DHCP isn’t assigning IPv4, the adapter is disabled, or the static configuration doesn’t match the router’s subnet.
Windows, macOS, Linux: confirm DHCP vs static IP
– If IPv4 is missing or shows 169.254.x.x: DHCP likely failed.
– If you recently changed network settings: ensure the Ethernet adapter isn’t set to a static IP that doesn’t match your router’s LAN subnet.
– If the interface is disabled: re-enable it—systems can show “connected” in a UI while the OS isn’t actually configured to route.
For exact steps, use your OS’s network settings panel and your router’s LAN subnet details.
A “default gateway” is the router’s LAN IP; without it, your device may still have an IPv4 address but can’t route traffic off-subnet (common with “connected but no internet”).
From my troubleshooting notes, the fastest way to avoid guesswork is to treat the IP screen like a contract: if IPv4 + gateway don’t line up with your router LAN range, Ethernet isn’t “working” even if the cable is fine—.
Run simple connectivity tests (gateway first, then internet)
If your Ethernet IP settings look correct, the next step is to test connectivity in the right order: gateway first, then public internet. This isolates whether the issue is local routing (LAN) vs WAN/provider vs DNS.
If you can successfully ping the router’s LAN IP (gateway) but not an internet IP, Ethernet is working locally and the remaining problem is usually DNS, WAN routing, or firewall policy.
Ping the router (gateway) first
Ping your router’s LAN IP (often 192.168.0.1, 192.168.1.1, or 10.0.0.1). If you can ping it, Ethernet works at the network layer—internet may still be misconfigured.
– Windows: use `ipconfig` to find “Default Gateway,” then `ping
– macOS/Linux: use `ip a` (or `ifconfig` on older systems) to find the default route/gateway, then `ping
If you don’t know it, use your router/admin guide for the gateway IP.
Ping a public IP (optional, but clarifying)
If pinging the gateway fails, internet won’t work either—so you stop there and focus on link/IP/DHCP. If gateway ping succeeds but public IP fails, the path from your device is broken (often routing/WAN/ACL issues, or a more specific LAN firewall rule).
Ping tests validate reachability at the IP layer; they do not confirm DNS, so “ping public IP fails” and “browser fails DNS” are different failure modes.
Use built-in tools only
Use what the OS provides; don’t rely on browser symptoms alone. Browser failures can be caused by DNS, captive portals, or app-level caching—ping gives you a clearer signal about whether Ethernet is actually transporting packets.
What can go wrong (and what each symptom usually means)
If Ethernet looks connected but nothing loads, the symptoms typically map to a predictable layer: physical link, IP/DHCP, routing, or DNS. The fastest strategy is to match what you see (“Link off,” “169.254,” “gateway unreachable”) to the layer that most likely failed.
“Ethernet link on but no internet” usually means physical connectivity exists, but either DNS resolution or router/WAN configuration is failing rather than the Ethernet cable.
Symptom-to-cause mapping (quick)
– Link light on, but no internet: physical link is present; DNS, gateway/router settings, or WAN-side issues are more likely. Try pinging your gateway first.
– Link light off: bad cable, wrong port, faulty adapter, or a switch/router port issue. Test with a different cable/port.
– “Unidentified network” / no IPv4 address: DHCP isn’t assigning an address—check router DHCP is enabled and your Ethernet interface isn’t disabled.
– Connected but very slow (e.g., 10 Mbps instead of 100/1000): negotiation/speed mismatch can happen with damaged cables or incorrect cabling category. Replace the cable if you suspect wear or damage.
– VLANs/managed switches: if you’re on a corporate network with VLAN tagging, a “connected” Ethernet link may still be blocked at the switch policy level.
Pros/cons of staying “quick and visual” vs going deep
- Pros (Quick checks)
- Fast isolation of physical link vs IP vs routing—often resolves issues in under 10 minutes.
- Lower risk than editing static routes or VLAN settings on managed networks.
- Cons (Quick checks)
- Can’t fully diagnose upstream provider/WAN policy issues without admin access.
- Won’t reveal VLAN permission blocks unless you can view switch policies.
Verdict: a practical recommendation (with downsides)
Start with link/activity lights and ping your router—those two checks quickly tell you whether Ethernet is physically connected and whether your network path works. If you get link + gateway reachability, the remaining issue is usually DNS or the router’s internet/WAN setup.
A successful ping to the default gateway is strong evidence that the Ethernet path and local routing are functioning; it sharply narrows troubleshooting away from DHCP/link negotiation.
Skip the deeper troubleshooting (or advanced settings) if:
– You don’t have admin access to the router/switch.
– You’re on a managed network where VLAN/security policies block connectivity.
– You’re uncomfortable editing network interface settings—because mistakes can break DHCP/static routing.
If you do have admin access, the next “step up” after gateway ping is usually DNS and WAN diagnostics on the router—not repeated cable swaps. And if you’re on 2026-era hardware with 2.5G/5G Ethernet, pay attention to negotiated speed; speed downgrades often point to cabling and pair integrity long before the internet fails completely.
Ethernet working checklist (scan/save)
| Check | What you should see | If not, try this |
|---|---|---|
| Cable seated both ends | Snug fit on PC + router/switch | Reseat; use another cable |
| Link light | On (or “Link detected”) | Try another port; replace cable |
| Activity light | Blinks during traffic | Reboot router/adapter; retry ping |
| Ethernet has IPv4 + gateway | IP address + default gateway visible | Check DHCP/static IP match |
| Ping gateway works | Reply from router | Router LAN issue; firewall rules; VLAN policy |
| Ping public IP/internet works | Replies to public destination | DNS issue or WAN/provider issue |
Sources
– Microsoft Learn / Microsoft Support documentation for Windows networking utilities and troubleshooting (e.g., `ipconfig`, `ping`, and network adapter/IP configuration concepts).
– Apple Support documentation for macOS network settings and connectivity troubleshooting (DHCP/IP configuration and diagnostics).
– Manufacturer documentation for Ethernet port indicators and link negotiation (router/switch/NIC manuals vary by model).
– IEEE 802.3ab (1000BASE-T) for copper Ethernet segment behavior and limits (speed negotiation/link design fundamentals).
– IEEE 802.3u (100BASE-TX) for 100BASE-TX copper segment design limits.
– RFC 3927 for IPv4 link-local addressing behavior (169.254.0.0/16) when DHCP is unavailable.
– IEEE/Ethernet standards overviews for background on link/activity and speed negotiation (for additional context).
Ethernet troubleshooting works best when you treat it like a layered checklist: confirm physical link, validate IP settings, then prove connectivity with a gateway ping. If you follow the order in this guide—especially the “link lights + ping your router” combination—you’ll usually identify the fault domain quickly without risky configuration changes, and you’ll know exactly whether the problem is your cable, your DHCP/IP settings, or something upstream.
Frequently Asked Questions
What are the signs that Ethernet is working on my computer?
Look for an active link indication on the Ethernet port—many network cards show a steady or blinking LED when a cable is connected. On your device, check that the connection status reads “Connected” or “Ethernet has a valid IP address” rather than “Unidentified network.” You should also see network activity lights increase when you browse or stream, confirming data is flowing.
How can I tell if my Ethernet cable is actually connected and negotiated correctly?
First, reseat the Ethernet cable on both ends and confirm it is fully clicked into place. Then check your network adapter details (Windows: Network Status or adapter settings; macOS/Linux: Network preferences or terminal commands) to verify link speed and that the interface is enabled. If you see “media disconnected,” “link down,” or no IP address assigned, the Ethernet link may not be established.
Why does my Ethernet show connected but no internet access?
This usually means the Ethernet link is up, but DNS, IP configuration, gateway, or ISP connectivity is failing. Try releasing and renewing the IP address, restarting the modem/router, and verifying the default gateway is correct. You can also test by pinging the router (for local connectivity) and then pinging a public site to distinguish between a local issue and an internet/DNS issue.
Which quick tests can confirm Ethernet is sending and receiving data?
Use a simple connectivity test such as pinging the router’s IP address (commonly 192.168.1.1 or 192.168.0.1) to confirm Ethernet traffic works locally. Then test an external host (for example, ping a public DNS IP) to verify internet routing. If available, check interface activity in your operating system’s network statistics or use built-in tools to confirm send/receive traffic over the Ethernet adapter.
What’s the best way to troubleshoot Ethernet when it won’t work?
Start with hardware checks: try a different Ethernet cable and, if possible, a different router/switch port to rule out a bad cable or port. Next, restart network components (computer, router, modem) and disable/enable the Ethernet adapter to force re-negotiation. Finally, verify IP settings (DHCP vs static), update or reinstall the Ethernet driver, and ensure there is no disabled network adapter or firewall rule blocking connectivity.
📅 Last Updated: October 25, 2026 | Topic: how to know if ethernet is working | Content verified for accuracy and freshness.
References
- Ethernet
- ethtool(8) – Linux manual page
- ip-link(8) – Linux manual page
- RFC 2863: The Interfaces Group MIB | RFC Editor
- Test-NetConnection (NetTCPIP) | Microsoft Learn
- ping(8) – Linux manual page
- https://scholar.google.com/scholar?q=ethernet+troubleshooting+check+link+status Google Scholar
- https://scholar.google.com/scholar?q=ethtool+link+detection+speed+duplex+how+to Google Scholar
- https://scholar.google.com/scholar?q=ethernet+network+connectivity+troubleshooting+ping+packet+counters Google Scholar
