Tutorials

Why Ethernet shows connected while internet access fails on Windows PCs

By Evander Thorne · November 16, 2026

Advertisement
Ad disclaimer: For links on this page, DESKING APP may earn a commission from the provider. This supports our work and has no influence on our editorial rating.
Why Ethernet shows connected while internet access fails on Windows PCs
Advertisement
Table of contents
  1. Why Ethernet Connects but Cannot Reach the Internet
  2. What connected means
  3. Isolate the fault
  4. Inspect the cable
  5. Read the IP settings
  6. Test the gateway
  7. Separate DNS failures
  8. Check router access
  9. Review VPN settings
  10. Repair the adapter
  11. Understand false alerts
  12. Handle office networks
  13. Verify the repair
  14. Frequently Asked Questions

Why Ethernet Connects but Cannot Reach the Internet

An Ethernet connection can show as active even when the computer cannot reach a website, because the cable link and internet access are separate stages of a network connection.

The adapter may detect a router or switch while the computer has no valid IP address, cannot reach its default gateway, uses an unavailable DNS server, or sits behind a router with no working internet service.

Windows reports the physical connection, but that status alone does not identify which stage has failed.

The quickest reliable fix is to test each stage in order.

Start by checking whether other devices can access the internet through the same router.

Then inspect the computer’s IP configuration, test the gateway, check DNS, and investigate the router or internet provider if the local network works.

This sequence applies mainly to Windows 10 and Windows 11, although the same network principles apply to macOS and Linux.

It also helps prevent unnecessary changes to a working office network.

What connected means

An Ethernet status of Connected confirms that the network adapter has detected a wired link.

It does not confirm that the computer received a usable network address, that the router can forward traffic, or that the internet provider has an active connection.

A link light on the computer or switch provides similar evidence: the physical connection has been established, but higher network functions may still fail.

A normal connection depends on several stages.

The Ethernet adapter and cable establish the physical link, DHCP usually provides the computer with an IP address, the default gateway routes traffic outside the local network, and DNS translates domain names into IP addresses.

The router must then have a working connection to the internet provider.

A fault at any stage can leave Windows showing an active Ethernet connection while browsers, email clients, and other online applications fail.

The Windows network icon can also report a problem even when some internet access works.

Windows uses its Network Connectivity Status Indicator, or NCSI, to test whether the computer can reach designated internet endpoints.

A firewall, proxy, VPN, DNS restriction, or enterprise network policy can interfere with that test.

Microsoft explains that a failed connectivity probe does not always prove that every internet destination is unreachable, so test an actual website or service before treating the icon as the final diagnosis.

Isolate the fault

The first task is to establish whether the failure affects one computer or the entire network.

Connect another device to the same router, preferably through the same Ethernet cable and port.

If the second device reaches the internet, the router’s internet connection is probably working and attention should move to the original computer.

If multiple wired and wireless devices fail, investigate the router, modem, provider connection, or wider network configuration.

A useful comparison must keep the network path consistent.

A laptop connected to Wi-Fi on another router does not prove that the Ethernet cable or switch port is working.

Test the same LAN port and cable where possible, then compare with another port or cable while changing only one item at a time.

Advertisement

This method identifies a faulty component without replacing several parts unnecessarily.

Before changing settings, record the time of the failure, the device affected, the cable or port in use, and whether Wi-Fi works on that same computer.

In an office, also record whether other users on the same switch or network segment have the problem.

These details help distinguish a local Windows fault from a shared infrastructure issue, especially when a managed switch, VLAN, firewall, or authentication system sits between the computer and the router.

Inspect the cable

A cable can establish a link while still causing unreliable communication.

Damaged conductors, loose connectors, a broken retaining clip, a poor wall termination, or a faulty switch port can interrupt traffic even when the adapter reports Connected.

Start with the simplest physical checks before changing IP or DNS settings.

A direct connection to a known working router LAN port can also eliminate a faulty wall socket, patch panel, dock, or intermediate switch.

Use this sequence to isolate the physical path:

  1. Reseat the Ethernet cable at both ends and confirm that each connector locks into place.

    VPN

    ExpressVPN

    4.7
    4.7

    ExpressVPN delivers fast Lightway speeds, audited no logs privacy, and reliable streaming access across new Basic, Advanced, and Pro plans.

    • Very fast Lightway protocol speeds
    • RAM only TrustedServer infrastructure design
    • Pricier than most mainstream competitors
    • No permanent free plan available
    Read review View Plans Affiliate Link

    Check the computer and router or switch for link lights, if the equipment provides them.

  2. Inspect the cable for crushed sections, sharp bends, exposed wiring, damaged clips, or loose connectors.

    Replace it with a known working cable if there is visible damage or uncertainty.

  3. Keep the same cable and computer, but move the connection to another LAN port on the router or switch.

    A single port can fail while the remaining ports continue to work.

  4. If the computer uses a USB Ethernet adapter or docking station, connect the adapter directly to the computer and check whether Windows detects it.

    A dock may also require external power or a compatible USB port.

  5. If the connection passes through a wall socket or office switch, test directly at an approved router or switch port.

    If direct access works, investigate the intermediate cabling or equipment.

Check that the cable enters a LAN port, not the router’s WAN or Internet port.

Those ports serve different purposes.

On a typical home router, the WAN port connects to the modem or provider equipment, while LAN ports connect computers and other local devices.

Microsoft’s Ethernet troubleshooting guidance makes this distinction because connecting a computer to the wrong port can prevent normal access even when the cable is physically attached.

Read the IP settings

An IP address reveals whether the computer has joined the local network correctly.

In Windows, open Command Prompt and run the command ipconfig /all.

Find the section for the active Ethernet adapter, not a Wi-Fi connection, VPN interface, Bluetooth adapter, or virtual network interface.

Record the IPv4 Address, Subnet Mask, Default Gateway, DHCP Enabled status, and DNS Servers.

A normal private IPv4 address on a home or small office network often begins with 192.168, 10, or a range from 172.16 through 172.31.

These ranges are commonly used for private networks, but the correct address depends on the router and network design.

A missing default gateway is a warning sign because the computer may be able to communicate with local devices but have no configured route to external networks.

An address beginning with 169.254 usually indicates that Windows assigned itself an automatic link local address after it did not receive a suitable address from a DHCP server.

This is commonly called an APIPA address.

It does not automatically mean that the Ethernet cable is defective.

The DHCP service may be unavailable, the switch port may be assigned to the wrong VLAN, a DHCP relay may have failed, or the network may require authentication before it assigns an address.

If DHCP is enabled on a normal home network, try requesting a new address.

Open Command Prompt as an administrator and run ipconfig /release, followed by ipconfig /renew.

The first command releases the current DHCP configuration; the second asks the DHCP server for a new lease.

If Windows continues to show a 169.254 address, focus on the DHCP server, router, cable path, switch port, or network access policy rather than changing DNS.

Advertisement

Do not assign a random static IP address to make the warning disappear.

A static address must match the network’s subnet, avoid addresses already in use, and use the correct gateway and DNS settings.

An incorrect static configuration can create an IP conflict or make the computer unreachable.

On a managed office network, ask the administrator whether the port uses DHCP, a reserved address, a fixed address, or a particular VLAN before changing anything.

Test the gateway

The default gateway is usually the local router or a network device that routes traffic beyond the computer’s subnet.

If the Ethernet adapter has a valid IP address and a gateway, test whether that gateway responds.

Use the gateway address shown by ipconfig /all with the ping command.

For example, if the displayed gateway is 192.168.1.1, run ping 192.168.1.1.

A successful response indicates that the computer can exchange IP traffic with the gateway.

It does not prove that the router has internet access, but it confirms that communication across the local network is working at that moment.

If the gateway does not respond, check the IP address and subnet mask, cable, switch port, VLAN assignment, and router LAN configuration.

Some networks block ping requests, so a failed ping alone is not conclusive; try opening the router’s management address if you are authorised to access it.

When the gateway is unreachable despite a valid address, check whether another device on the same network can reach it.

If other devices work, investigate the computer’s adapter, local firewall, VPN software, or IP configuration.

If several devices on the same switch or VLAN fail, the issue may involve the switch, router interface, access control, or network segmentation.

Avoid changing the gateway address unless the network administrator confirms the correct value.

Separate DNS failures

DNS is responsible for translating a name such as example.com into the IP address used to reach the destination.

If the computer can reach an external IP address but cannot open websites by name, DNS becomes a likely cause.

This distinction matters because changing the Ethernet cable or reinstalling the network driver will not normally repair an unavailable DNS resolver.

Test name resolution only after confirming that the computer has a valid address and can reach its gateway.

Run nslookup example.com in Command Prompt.

The result should show the DNS server used for the query and the address returned for the domain.

If the request times out or reports that the domain cannot be found, check the configured DNS server and compare the result with another device on the same network.

A company network may use internal DNS servers to resolve private services, so a public resolver is not automatically an appropriate replacement.

If the computer uses automatic DNS, renew its network configuration and clear the local DNS cache with ipconfig /flushdns.

Then test the same website again.

If the network administrator permits external DNS, you can temporarily test a reputable public resolver to determine whether the configured DNS server is responsible.

Restore the approved setting after the test, particularly on a business network that relies on internal domain names, filtering, or security policies.

Advertisement

Check router access

A working gateway does not guarantee that the router has an active connection to the internet.

The router may be online locally while its WAN interface has lost the provider connection, failed to authenticate, or received no usable address from the modem.

Check the router’s internet or WAN status through its management interface, using the manufacturer’s documented access method.

VPN

ExpressVPN

4.7
4.7

ExpressVPN delivers fast Lightway speeds, audited no logs privacy, and reliable streaming access across new Basic, Advanced, and Pro plans.

  • Very fast Lightway protocol speeds
  • RAM only TrustedServer infrastructure design
  • Pricier than most mainstream competitors
  • No permanent free plan available
Read review View Plans Affiliate Link

Look for the WAN address, connection state, and any reported provider or authentication error.

If all devices have lost internet access, inspect the modem and router indicators before restarting them.

A provider outage, damaged fibre or coaxial connection, failed optical terminal, or account authentication issue may affect the WAN connection.

If the equipment is separate, restart the modem first and allow it to complete its startup before restarting the router.

Microsoft recommends waiting for the modem to stabilise before powering the router again, because the router needs an active upstream connection to establish internet access.

A normal restart is different from a factory reset.

Restarting power cycles the equipment while retaining its configuration.

A factory reset can erase the Wi-Fi name and password, provider credentials, VLAN settings, port forwarding rules, DHCP reservations, firewall policies, and other custom configuration.

Do not use the reset button as an early troubleshooting measure, especially on equipment supplied or managed by an internet provider.

Contact the provider if the WAN status remains disconnected or the modem reports a line or optical fault.

Review VPN settings

A VPN can change the computer’s routing table and DNS configuration.

If the VPN client connects incorrectly, routes traffic through an unavailable gateway, or enforces a policy that blocks access, Windows may show Ethernet as connected while applications cannot reach the internet.

Disconnect the VPN temporarily only if your organisation permits it, then test a normal website.

If access returns, the physical Ethernet connection may be healthy and the VPN configuration needs attention.

Corporate VPNs sometimes use full tunnel routing, which sends most or all internet traffic through the organisation’s network.

A failed VPN gateway or an incorrect route can therefore affect internet access even when the local router works.

Split tunnel configurations behave differently because selected traffic uses the VPN while other destinations use the local connection.

Do not delete VPN profiles or change route settings to restore access without checking the organisation’s policy.

Proxy settings can produce a similar symptom.

In Windows, open Settings, select Network & internet, then Proxy.

Check whether a manual proxy or setup script is enabled.

A proxy that is no longer available can prevent browsers and applications from reaching websites, even when basic IP connectivity works.

Do not disable a company managed proxy or automatic configuration script without authorisation, since it may be required for internet access, filtering, or security inspection.

Advertisement

Repair the adapter

If another device works through the same cable and port, and the computer has no obvious IP or DNS problem, inspect the Ethernet adapter in Windows.

Right click Start, open Device Manager, and expand Network adapters.

Find the wired adapter, which may carry a manufacturer name such as Intel or Realtek.

A warning symbol, disabled device, or missing adapter can indicate a driver or hardware problem.

Open the adapter’s Properties and check the Device status message on the General tab.

If Windows reports a device error, record the code before changing the driver.

You can try enabling the adapter if it is disabled, or updating its driver through Windows Update or the computer manufacturer’s support page.

Prefer a driver designed for the exact computer model and Windows version rather than a generic download from an unfamiliar driver website.

If the connection failed immediately after a driver update, use the Roll Back Driver option when it is available.

If updating or rolling back does not help, download the correct driver in advance, then uninstall the Ethernet adapter from Device Manager and restart Windows.

Windows may reinstall a compatible driver during startup.

Keep the manufacturer’s driver installer on a USB drive if the affected computer has no alternative internet connection.

Network Reset is a later option, not a first response.

In Windows 11, open Settings, select Network & internet, Advanced network settings, then Network reset.

Choose Reset now and allow the computer to restart.

This removes installed network adapters and restores their settings to default values.

It can also require you to reinstall VPN clients, recreate virtual switches, restore custom IP settings, or reconnect to managed networks, so record those settings before using it.

Understand false alerts

Windows does not decide internet availability solely by checking whether the Ethernet adapter is connected.

Its Network Connectivity Status Indicator performs network probes and evaluates responses to determine whether the system has internet access or only local connectivity.

Microsoft documents that proxies, VPNs, DNS failures, and blocked probe requests can affect this assessment.

A computer may therefore display No Internet even when a browser can reach some websites or internal services.

Test more than the taskbar icon.

Open a browser and try a known working website, then test a second unrelated site.

If both load, but Windows still reports no internet, investigate whether a proxy, firewall, DNS filter, or enterprise security policy blocks the connectivity probe.

Microsoft advises against disabling active probing as a general fix.

The indicator is useful, but it should not replace tests of the applications and destinations that matter.

A more detailed investigation is available in Event Viewer.

Open Applications and Services Logs, expand Microsoft, then Windows, and inspect the NCSI operational log.

The entries can help identify failed connectivity probes and the time they occurred.

On managed computers, an administrator can correlate these events with firewall, proxy, DNS, and packet capture records.

Avoid editing registry values or disabling NCSI services simply to remove the warning; that can hide a real fault without restoring access.

Advertisement

Handle office networks

A business Ethernet connection can depend on settings that do not exist on a basic home router.

Managed switches may assign ports to specific VLANs, use 802.1X authentication, apply access control lists, or rely on DHCP relay to reach a central address server.

If the port is assigned to the wrong VLAN, the computer may receive no address, receive an address from the wrong subnet, or reach local resources without access to the expected gateway.

When only one office desk is affected, compare its switch port configuration with a working port in the same department or network segment.

Check whether the switch reports the port as active, whether authentication succeeded, and whether the correct VLAN is assigned.

A cable link light does not confirm that 802.1X authentication has passed or that the port is authorised to carry user traffic.

Do not move a company computer to an arbitrary switch port, since the replacement port may have different security or network policies.

A missing DHCP lease across several users can indicate a DHCP server or relay problem.

If the DHCP server is reachable but a particular scope has no available addresses, new devices may fail to obtain a lease while existing devices continue to work until their leases expire.

VPN

ExpressVPN

4.7
4.7

ExpressVPN delivers fast Lightway speeds, audited no logs privacy, and reliable streaming access across new Basic, Advanced, and Pro plans.

  • Very fast Lightway protocol speeds
  • RAM only TrustedServer infrastructure design
  • Pricier than most mainstream competitors
  • No permanent free plan available
Read review View Plans Affiliate Link

The administrator should check the relevant scope, lease availability, relay configuration, and server logs.

A computer showing a 169.254 address is useful evidence, but it does not identify which part of the DHCP path failed.

Record the affected computer name, switch port, adapter MAC address, IP address, gateway, DNS servers, VLAN if known, and the time the problem began.

Share these details only with the authorised IT team, because network configuration and hardware identifiers can reveal internal infrastructure.

Avoid publishing the complete output of ipconfig /all in public forums.

It can expose host names, DNS suffixes, addresses, and other details that should remain within the organisation.

Verify the repair

A connection should be considered restored only after the computer can reach the destinations it needs.

Check that Windows has a valid address and default gateway, confirm that the gateway responds where ping is permitted, and verify that DNS resolves normal domain names.

Open several websites and test the applications that originally failed.

If the computer relies on a corporate VPN, internal DNS, or a business application, verify those services separately after the basic internet connection returns.

If the fault returns, preserve the evidence rather than repeating every reset.

Note whether the failure follows the computer, cable, switch port, or network segment.

A problem that follows one computer points toward its adapter, driver, configuration, or security software.

A problem that follows a particular port or wall socket points toward the physical path or switch configuration.

A network wide failure points toward shared infrastructure or the provider connection.

The most useful troubleshooting record contains the original symptom, the tests performed, their results, and the single change that restored access.

This makes a recurring fault easier to diagnose and reduces the risk of losing working settings during a future repair.

It also gives an ISP or network administrator specific evidence to investigate instead of a general report that Ethernet is connected but the internet does not work.

Frequently Asked Questions

Why does Ethernet work but Wi-Fi does not?
Ethernet and Wi-Fi use different network adapters and connection paths, so one can work while the other fails. If Ethernet works but Wi-Fi does not, investigate the wireless adapter, access point, wireless authentication, and signal conditions. If Wi-Fi works but Ethernet fails, focus on the cable, LAN port, wired adapter, switch, VLAN, or Ethernet driver. Testing both connections on the same computer helps identify which path needs attention.
Can a bad Ethernet cable show as connected?
Yes. A damaged cable or connector can sometimes establish a physical link while causing packet errors, intermittent communication, or reduced link speed. A link light does not certify that every cable pair is working correctly. Replace the cable temporarily with a known working one and keep the router port and computer unchanged. If the connection becomes stable, inspect the original cable and its connectors rather than changing Windows network settings.
Does a 169.254 address mean the router is broken?
No. A 169.254 address usually means the computer did not receive a suitable DHCP address and assigned itself a link local address. The cause may be the router’s DHCP service, a switch port, a VLAN, a DHCP relay, a cable path, or network authentication. Check another device on the same port and network segment before concluding that the router has failed. On a business network, ask the administrator to inspect DHCP and port configuration.
Why can I access the router but not websites?
Access to the router proves that the computer can communicate with at least part of the local network. It does not prove that the router has a working WAN connection or that DNS can resolve website names. Check whether another device has internet access, test an external IP address, and run nslookup for a domain. If local access works but external destinations fail, investigate the router’s WAN status, DNS configuration, firewall, and internet provider.
Should I change my Ethernet IP address manually?
Only if the network requires a static address and you know the correct configuration. Most home networks use DHCP to assign addresses automatically, while business networks may use DHCP reservations, static assignments, or VLAN specific settings. Choosing an address at random can create a conflict or place the computer outside the correct subnet. If the adapter previously used automatic configuration, restore automatic IP and DNS settings unless the network administrator instructs otherwise.
Sources5

External pages are independent third-party sources. Desking App does not control or endorse their content and accepts no responsibility for it. Visiting them is at your own responsibility and risk.

Advertisement

Liked this? Get the next one in your inbox