ProblemEthernet connected confirms a link, not a usable IP configuration or Internet access. Separate cable/port, received configuration and service access. Comparisons must use the same router and one connection at a time so Wi-Fi does not mask the wired failure.

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

  1. Confirm the failure really occurs over EthernetSeparate link state and browsing without another connection distorting the result.

Find your situation

See all the clues. Choose the one that matches what you observe.

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

01

Confirm the failure really occurs over Ethernet

Separate link state and browsing without another connection distorting the result.

  1. 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.

    1. Settings
    2. Network & internet
    3. Ethernet
  2. 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.

03

Compare the wired path with another device

  1. 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.

  2. 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.

04

Check the router’s shared access

  1. If several devices fail on wired and Wi-Fi connections, check modem/router indicators and provider notices using another available connection. This places the investigation upstream of each PC; it does not alone prove a provider outage.

  2. On your home network, warn that sessions will disconnect and power-restart the modem/router according to its manual. Do not press factory reset. Wait for service recovery and test two devices: if both still lack access, escalate to the provider with those results.

  3. If only one recovers, switch to the local branch for the failing device. On a managed network, IT coordinates the equivalent test; do not change VLANs, authentication or port policy.

05

Read address, gateway and DNS without changing them

  1. Command Prompt
    ipconfig /all

    In 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.

  2. 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.

  3. 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.

06

Test name resolution before changing DNS

  1. Command Prompt
    nslookup www.microsoft.com

    Queries the configured DNS server without changing it. Check whether it returns addresses for the queried name, as well as identifying the responding server.

  2. 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.

  3. 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

Advanced checks

Continue if the earlier steps did not help. Read each procedure’s precautions first.

07

Request DHCP only for the affected adapter

  1. 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.

  2. Command Prompt
    ipconfig /renew "Ethernet"

    Requests DHCP configuration for the named adapter; it does not first release addresses or reset the whole network stack.

  3. 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.

Next step

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.

Source review: . A documentation review, not a physical hardware test.

Related problems