Ethernet is connected but there is no internet: a link light shows electrical connection, not a valid IP route. Compare cable/port, DHCP address, router LAN status and another wired device. Check the device's IP address; a 169.254 address means it never received one from DHCP.
Differential
Likely causes of “Ethernet is connected but there is no internet”, and how to tell them apart
- 1
The device did not receive an IP address from the router
What separates it The device shows a 169.254 address or no address, and the cable light is on because the link is electrically up.
How to confirm Check the device's IP address; a 169.254 address means it never received one from DHCP.
- 2
The cable or port is faulty
What separates it The link light flickers or the speed shows as 10 or 100 Mbps, and a different cable or port works.
How to confirm Swap in a known-good cable and a different LAN port on the router.
- 3
A switch, powerline adapter or wall jack in the path has failed
What separates it Devices on the far side of the switch or adapter have no internet while the router's own ports work.
How to confirm Plug the device directly into the router to bypass everything in between.
- 4
A VLAN or static IP setting does not match the network
What separates it The device has a manually set address, or the port is on a different VLAN, so it cannot reach the gateway.
How to confirm Switch the adapter back to automatic addressing and look at any manual settings.
Before you touch a setting
Record this first — changing settings destroys the evidence
- The device's IP address, gateway and DNS server as it shows them.
- The cable and port used and what lies between the device and the router.
- Whether another wired device on the same port works.
Try in this order
0 of 4 completedCapture the exact symptom
ReversibleCheck the device IP and gateway; a 169.254 address usually means it did not receive DHCP.
Run the smallest isolation test
ReversibleTry a known-good cable and LAN port, bypass switches/powerline adapters and renew automatic networking.
Correct only the proven cause
ReversibleReplace the failed segment or correct VLAN/static-IP settings; leave ISP WAN troubleshooting to all-device failures.
Verify before changing anything else
ReversibleTransfer locally and load internet sites for ten minutes on the repaired path.
Stop boundary
When this stops being a self-service repair
- !Leave ISP-side WAN troubleshooting for the case where every device on the network has no internet, not just this one.
Evidence ledger
Sources behind this answer
Exact questions
Common questions
What does a 169.254 address mean?+
The device could not get an address from a DHCP server and gave itself one. It usually points at the cable, the port or the router's DHCP service.
Why no internet on Ethernet?+
The router may lack a connection from the modem, or the device has a wrong IP setting.
Is DHCP a factor?+
Yes, the device should get an address automatically.