Ethernet connected but no Internet
Windows detects a connected Ethernet link, but Internet access fails. A physical link does not establish that the router has Internet access: separate cable, port, PC and network.
Try this first
1 quick checks · ~3 min
Find your situation
See all the clues. Choose the one that matches what you observe.
The link drops or shows disconnected
Test cable and port before changing DNS or IP configuration.
Wi-Fi works but Ethernet does not
Compare the same cable/port with another device and inspect the correct adapter’s configuration.
Other devices fail too
Investigate the router’s shared access before repairing Windows.
Diagnostic signals
- ObservationAutomatic 169.254 IPv4 and no IPv4 gateway
- With DHCP enabled, this points to missing received IPv4 configuration. It does not identify the faulty component or rule out independent IPv6 connectivity.
- ObservationOnly one site fails
- If others load over Ethernet, connectivity exists. Investigate the site or its name resolution rather than reinstalling the adapter.
Step-by-step solutions
Confirm the failure really occurs over Ethernet
Separate link state and browsing without another connection distorting the result.
Record the state. For the comparison temporarily disable Wi-Fi only if you do not depend on it for a remote session; restore it afterward. Open two known sites.
- Settings
- Network & internet
- Ethernet
If only one site fails, follow its diagnosis. If disconnected or alternating states, follow the link branch. If Ethernet stays connected but nothing loads, compare Wi-Fi on the same router and another device to choose local or shared failure.
Isolate cable, port and intermediate adapters
Finish transfers and warn others before disconnecting. At home, connect to a router LAN port, not WAN/Internet. Try another known cable and then another LAN port, changing one thing at a time; do not move office cables without IT.
If link and browsing return after changing one element, keep that combination and stop. If a dock, USB adapter or wall socket is involved, record those components; an authorized direct test helps localize them without assuming the network card is damaged.
If the link is now stable but Internet is absent, move to configuration. Do not keep swapping cables if the symptom changed from physical disconnection to missing access.
Compare the wired path with another device
Use another authorized device on the same cable and port, with Wi-Fi inactive during the test. If it also fails, the router may have a wired-side problem even when Wi-Fi works; give that evidence to its owner rather than reinstalling Windows.
If the other device browses, focus on this adapter and its configuration. If no other device is available, leave that comparison pending and read the configuration; do not mark the cable or router as ruled out.
Read address, gateway and DNS without changing them
ipconfig /allIn Command Prompt, displays configuration without changing it and requires no administrator rights. Read the physical Ethernet adapter block, not Wi-Fi, VPN or a virtual one. Keep its exact name for any later test.
With DHCP enabled, automatic 169.254.x.x IPv4 and an empty IPv4 gateway point to missing IPv4 assignment. If other devices on that path also fail, contact the DHCP/port administrator. If only this device fails, the bounded renewal below can test a new request. IPv6 may still work: do not conclude the entire network is down.
If DHCP is disabled and settings are manual, confirm them with whoever configured the network; do not invent an IP or gateway. With apparently valid configuration, move to name resolution. Having a private IP does not prove the Internet route works.
Test name resolution before changing DNS
nslookup www.microsoft.comQueries the configured DNS server without changing it. Check whether it returns addresses for the queried name, as well as identifying the responding server.
A response containing addresses confirms that lookup, not that the browser or all Internet access works. A timeout means no answer arrived in time; the cause can be server, route or filtering, not proven cache corruption. Compare with the other device and take the results to IT/provider.
If browsing shows a specific DNS error, follow the related guide for that error. If DNS responds but several pages still fail only on this PC, run Get Help > Network and Internet and keep the result; review proposed changes before accepting them. Do not disable managed firewall/VPN protection to force a result.
Advanced checks
Continue if the earlier steps did not help. Read each procedure’s precautions first.
Request DHCP only for the affected adapter
Use this test only with DHCP enabled, a stable link and missing IPv4 configuration on this device. Open Command Prompt as administrator. If the adapter is not named exactly Ethernet, replace that quoted name with the one you read; do not omit the name because it would affect other adapters.
ipconfig /renew "Ethernet"Requests DHCP configuration for the named adapter; it does not first release addresses or reset the whole network stack.
Read ipconfig /all again and test browsing. If it obtains an address and gateway and browses, stop. If it times out contacting DHCP, keep the message and escalate communication with that server/port. If it obtains configuration but cannot browse, move to DNS; do not renew indefinitely.
Still not working?
Stop when stable browsing returns. If it persists, give support the link state, cable/port/device comparison and relevant configuration output with private data hidden. Do not publish MAC addresses, internal names or full configuration. Do not uninstall drivers or reset networks/VPNs without a hypothesis and a recovery method.
Sources
Documentation behind this guide. Editorial recommendations are identified separately.
- Microsoft SupportOfficialFix Ethernet connection problems in Windows
- Microsoft LearnOfficialipconfig
- Microsoft LearnOfficialIP_PER_ADAPTER_INFO — Automatic Private IP Addressing
- Microsoft LearnOfficialnslookup
Source review: . A documentation review, not a physical hardware test.
Related problems
Wi-Fi connected but no internet
Joining Wi-Fi does not guarantee internet access. Compare another device on the same network to separate a PC-specific problem from a local-network or provider-side issue.
View solutionInternet keeps disconnecting
Connectivity works, then drops again. Record which devices and connection types fail together; that pattern is more useful than repeatedly resetting the network.
View solution