In this guide
Start by writing down exactly what Windows shows under Settings > Network & internet > Ethernet. “Not connected,” “Connected, no internet,” and a connection that drops under load are not interchangeable. One minute spent reading the link and IP state can prevent an unnecessary driver reinstall or a disruptive reset.
No link light, Media disconnected, or no internet
| Observed state | What it proves | Best next test |
|---|---|---|
| No LEDs at PC or router; Media disconnected | No physical Ethernet link | Known-good cable and another LAN port |
| Link LEDs on; IPv4 begins 169.254 | Adapter linked but did not receive DHCP lease | Another device on the same cable/port |
| Valid private IPv4 and gateway; no web | Local network may be up | Ping gateway, then test DNS and VPN |
| Works until sleep or a recent update | Power management or driver is plausible | Restart, driver version, rollback evidence |
| Wi-Fi and Ethernet both fail on all devices | Not an Ethernet-only PC fault | Router, modem, and ISP status |
1. Prove the physical link first
Push the connector into the PC and a numbered LAN port on the router until each latch seats. Do not use the router’s WAN or Internet port for the PC. Look for link or activity LEDs on both ends, if the hardware provides them. A dark port is useful evidence, not a reason to change DNS.
Replace only the cable with one known to work, then move only the router LAN port. If the computer uses a USB Ethernet adapter or dock, connect the adapter directly and test another compatible USB port. Avoid changing cable, dock, driver, and router at the same time; a successful test would not reveal which change mattered.
Microsoft also recommends testing the same network with another PC or adapter. If a second device fails on the same known-good cable and router port, investigate the router or upstream connection. If it works, return to the Windows adapter. For the related Arabic path, see Ethernet connected with no internet: link, IP, and DNS.
2. Read the adapter and address state
Open Settings > Network & internet. Ethernet should show Connected beneath the network name. Next, open Terminal or Command Prompt and run ipconfig /all. Do not publish or send the full output because it can contain device and network identifiers. Record only the Ethernet adapter’s status, IPv4 pattern, default gateway presence, and whether DHCP is enabled.
- Media disconnected: Windows does not see a physical link. Return to cable, port, dock, and adapter.
- 169.254.x.x: Windows assigned itself an APIPA address because DHCP did not provide one.
- 192.168.x.x, 10.x.x.x, or 172.16-31.x.x with a gateway: local addressing exists; test the gateway before blaming the adapter.
- Valid address but no default gateway: inspect DHCP or manual IPv4 settings.
Do not paste an address from another computer into IPv4 settings. Duplicate or incorrect static addresses create a second fault. If your workplace manages the device, record the state and contact IT before changing proxy, DNS, certificate, VLAN, or security software.
3. Separate gateway, internet, and DNS
Run ping followed by the default gateway address shown by ipconfig. A reply means packets reach the router; it does not prove that the internet or DNS works. Then test a well-known public address approved for your environment, and finally a domain name. An address works while a name fails is DNS-shaped evidence. Neither works while the gateway replies points upstream or to filtering.
Pause a VPN using its normal disconnect control, not by deleting it. Check Settings > Network & internet > Proxy for an unexpected manual proxy. If Ethernet says Connected but pages fail, use the DNS response and browsing checklist. If Wi-Fi works and Ethernet alone does not, keep the diagnosis on the wired path.
4. Use Windows diagnostics before destructive changes
On Windows 11, Microsoft currently directs users to the Network and Internet troubleshooter in the Get Help app. Run it and save the result. Then disable and re-enable the Ethernet adapter once under Advanced network settings. Restart the computer, especially if the problem began after an update or resume from sleep.
Microsoft lists a command sequence for resetting Winsock and TCP/IP, renewing the address, and flushing DNS. Use an administrator terminal only after recording the original state, and run commands in the documented order. A simple ipconfig /release may temporarily drop a remote session, so do not do this while relying on the affected connection for remote work.
5. Check the driver with a rollback plan
Open Device Manager > Network adapters and identify the Ethernet device by exact name. A warning icon, missing adapter, or error code is meaningful. If the failure started immediately after a driver update, inspect Properties > Driver for the version and date, then use Roll Back Driver when available and justified.
If you uninstall the adapter, Microsoft advises obtaining the manufacturer’s driver first, particularly when the PC has no alternate internet connection. After restart, Windows normally redetects the adapter. Download drivers from the PC or adapter manufacturer for the exact model, not from an unrelated driver-download site. For devices that fail at USB level, use the USB device, power, and driver isolation guide.
6. Keep Network Reset for last
Go to Settings > Network & internet > Advanced network settings > Network reset only after the cable, router port, address state, troubleshooter, and driver have been checked. Microsoft says this removes installed network adapters and their settings, then reinstalls them after restart. It may require you to reinstall or reconfigure VPN clients and Hyper-V virtual switches, and network profiles may return as Public.
Before selecting Reset now, save VPN installers and configuration, note static IP or DNS values, close work, and ensure you can sign in locally after restart. Network Reset cannot repair a broken latch, dead router port, or unsupported USB dock.
Evidence to keep if the fault returns
- PC model, Ethernet adapter name, driver version, and Windows build.
- Link-light state at both ends and results with a known-good cable and LAN port.
- Whether
ipconfigshowed disconnected, 169.254, or a valid gateway. - Whether another device worked on the same cable and router port.
- The exact time of failure and whether it followed sleep, an update, VPN use, or a dock connection.
Frequently asked questions
Should I use Network Reset first?
No. Microsoft presents it as the last step because it removes adapters and settings and can disrupt VPN or virtual networking.
Does a green Ethernet light prove internet access?
No. It proves a physical link at that port. DHCP, gateway, DNS, router, or ISP access can still fail.
Why does Ethernet show 169.254?
Windows has a physical link but did not receive a DHCP address. Test the same cable and router port with another device before reinstalling the driver.
Sources and review
- Microsoft Support: Fix Ethernet connection problems in Windows
- Microsoft Support: Essential network settings and tasks
- Microsoft Learn: ipconfig command reference
Reviewed by the SMSM Hub editorial team on July 23, 2026. Managed, VLAN-tagged, and enterprise networks may require administrator-specific settings before any reset.