A wired network can appear connected even when your Windows 11 PC cannot reach the internet. Work through these checks in order, preserving your existing configuration and identifying the failing part of the connection before attempting disruptive resets.
Why An Ethernet Connection Can Still Have No Internet
An Ethernet connection is a link between your computer and another piece of network equipment. A functioning cable and adapter can establish that link without providing access to websites, cloud applications or other external services. Windows may recognize the cable and identify a network while the computer still lacks a usable IP address, a route to the internet or working name resolution.
A typical home connection involves the PC, the cable, a router or switch, the router’s upstream broadband connection and the external internet. Each can fail independently. In an office, the path may additionally involve a managed switch, authentication system, separate network segment and security policy. A connection indicator alone does not tell you which part is working.
Start with evidence that separates these components. Compare the affected computer with a second device, determine whether the wired link is stable, inspect the address assigned to the Ethernet interface and test the local gateway. Only then investigate external connectivity and DNS. This order can prevent changes to a working driver or router when the actual fault is somewhere else. Read our Ethernet explanation for background on the wired link itself.
Step 1: Determine Whether The Problem Affects One Computer
Open a familiar website and another independent website in the browser. Try a separate internet-connected application, if available. If only one website fails, the problem may concern that service rather than the entire connection. If a browser fails but other applications communicate normally, review the browser or its proxy configuration before modifying network settings.
Check whether a phone or another computer can access the same destinations through the household router. If you use a phone, temporarily disable cellular data so that you do not accidentally test the mobile network instead of the home connection. Restore the original mobile data setting afterward.
If another device can use the internet, compare a wired connection through the same router if practical. A working Wi-Fi client establishes that the router can provide at least some internet service, but it does not prove that every LAN port, wired network segment or device-specific policy works. If both wired and wireless devices fail together, the shared gateway or provider deserves attention. Our router and ISP diagnosis guide covers that separate investigation.
Record when the issue began and whether it followed a cable move, Windows update, router change, docking station replacement or security software installation. A recent change is a useful clue, not a diagnosis. Avoid reversing every recent update indiscriminately.
Step 2: Inspect The Cable, Port, And Adapter
Confirm that the Ethernet cable is seated at both ends. Use an ordinary LAN port on the home router or approved network switch. The port reserved for the router’s upstream internet connection is not normally the correct place for a client PC. Look for bent connectors, damaged latches and visible cable damage. Do not force a connector into an incompatible socket.
If the equipment has link indicators, note their behavior. A link indicator can show that the devices have negotiated a physical connection, but its presence does not prove that IP communication works. Indicator colors and patterns are manufacturer-specific. Compare them with the documentation instead of assuming that green or amber has a universal meaning.
Try a known-good cable without changing other equipment, then repeat the same connection test. If necessary, try another authorized LAN port on the router. Change one variable at a time. Replacing both the cable and port simultaneously may restore the connection but leave the original fault unidentified.
If the computer uses a USB Ethernet adapter or docking station, check that it is connected securely and supported by the computer. Connect the adapter directly to an appropriate USB port if the manufacturer’s instructions permit that test. A dock may require its own power supply or firmware. Other devices working through the dock do not necessarily prove its Ethernet interface is functional. Microsoft’s Ethernet troubleshooting guidance supports cable and connection checks as an initial diagnostic step.
Step 3: Check The Ethernet Interface In Windows 11
Open Settings and choose Network & internet. Inspect the current network status and select Ethernet to view the available properties. The information displayed depends on the Windows version, adapter and network configuration. Determine whether Windows sees the wired network rather than merely assuming that a cable is active.
If the Ethernet interface is disabled, use the documented network adapter controls to enable it. Managed workplace computers may intentionally restrict particular interfaces, so do not override organizational policy. If the interface is completely absent from Settings and Device Manager, the problem may involve hardware detection, an adapter driver, a dock or firmware.
Open Device Manager from the Start menu and expand Network adapters. Identify the wired adapter by its manufacturer or model information. A warning symbol indicates that Windows has reported a problem, but the device properties and status message provide more useful context. A working entry does not establish that traffic can reach the gateway.
For a PC with both Wi-Fi and Ethernet, briefly disconnect Wi-Fi while testing the wired path if doing so will not disrupt important work. Otherwise, successful browsing might be using the wireless interface. Do not disconnect a network remotely if you depend on it to control the PC. If you are using Remote Desktop or another remote management session, arrange local access before changing adapter state.
Step 4: Inspect The Assigned IP Configuration
Open Command Prompt from the Start menu. Type the following command and press Enter:
ipconfig /all
This command displays detailed IP configuration for the computer’s interfaces. It is an inspection step and does not change their settings. Locate the Ethernet adapter associated with your physical cable; ignore unrelated virtual interfaces, disconnected Wi-Fi adapters and VPN entries unless they are involved in your specific setup.
Look at the assigned IPv4 and IPv6 addresses, default gateway, DHCP status and DNS servers. In many home networks, the router provides IPv4 configuration through DHCP. A common home network might use addresses in the 192.168.1.x range, but your actual network may use another private range or a different addressing arrangement. Do not copy example addresses to your computer.
If the Ethernet section shows Media disconnected, Windows does not currently recognize an active connection on that interface. Return to the cable, adapter and port checks. If the adapter has an IPv4 address beginning with 169.254 and no normal gateway, it may have assigned itself a link-local address because it could not obtain the expected DHCP configuration. This is distinct from an established route to the wider internet.
IPv6 can coexist with IPv4, and some legitimate networks operate differently from a typical dual-stack home network. Do not disable IPv6 as a generic troubleshooting step. Review the intended network configuration before interpreting a missing IPv4 gateway as definitive proof of complete internet failure. Microsoft’s ipconfig reference explains the values and command options. Our guides to DHCP and IP addresses provide additional context.
| Observation | Next Investigation |
|---|---|
| Media Disconnected | Cable, Port, Adapter Or Dock |
| Unexpected 169.254 IPv4 Address | DHCP And Local Network Access |
| Gateway Works, Websites Fail | External Route, DNS Or Policy |
| All Household Devices Fail | Shared Router, Broadband Or Provider |
Step 5: Test The Local Default Gateway
When the Ethernet adapter has an expected address and gateway, test the local route. For example, if the actual default gateway displayed for your Ethernet interface is 192.168.1.1, run:
ping 192.168.1.1
Replace the example with the address shown by your computer. A successful response indicates that the exchange of ICMP echo messages with that gateway is working at the time of the test. It does not establish that the gateway can reach every external destination or provide sufficient throughput.
A timeout can have several explanations. The gateway may not be reachable, the computer may have incorrect addressing or the equipment may ignore this kind of diagnostic request. Compare the result with other evidence. If you are authorized to administer your home router, try its documented local management address. If you can reach the local interface, the cable and local IP path are functioning at least for that communication.
Do not assume that a failed gateway ping requires replacing the router. Confirm the cable, port and address assignment first. On a workplace network, the designated gateway might not expose a management page to ordinary users. Its security configuration can prevent diagnostic traffic even if internet service is healthy.
Our router guide explains why a gateway is normally involved when traffic leaves a local subnet. The decisive question at this stage is whether the Ethernet-connected PC can reach the expected network beyond its own interface.
Step 6: Distinguish DNS Failure From External Connectivity Failure
If the gateway is reachable, inspect what happens when the computer communicates beyond it. Try a familiar external site. You can also use Command Prompt to ask a DNS resolver for an address associated with a known domain:
nslookup example.com
A successful lookup establishes that this query received a response, not that the website itself is accessible. A failed lookup may reflect an unavailable DNS resolver, incorrect DNS configuration, an external path failure or filtering. Compare several legitimate destinations before deciding that name resolution is the only problem.
In PowerShell, an optional focused check is Test-NetConnection example.com -Port 443. The command attempts to test a TCP connection to the named endpoint and port; it depends on resolving the name and reaching that particular service. A successful result does not establish that every HTTPS application works, since browser policies, TLS and application behavior can introduce further requirements. A failed result does not prove that the entire internet is unavailable.
If another device on the same network resolves names and opens websites while Ethernet on the PC does neither, inspect the computer’s addressing, security and proxy settings. If multiple clients fail to resolve names, the configured DNS service or shared path deserves attention. See what DNS does for the distinction between names and addresses.
Do not disable security controls or substitute an arbitrary DNS service simply to make a test succeed. Some workplaces require internal name resolution. On a household network with an intentionally configured private service, record the existing settings and identify the reason for failure before making changes.
Step 7: Renew DHCP Configuration When Appropriate
If the computer is meant to obtain its IPv4 configuration automatically and the address appears missing or unsuitable, try reconnecting the Ethernet cable or restarting the affected computer. These steps can trigger a fresh negotiation without requiring permanent configuration changes.
If the issue persists, obtain the exact interface name shown by ipconfig. For an interface actually named Ethernet, the following Command Prompt examples target that interface:
ipconfig /release "Ethernet"ipconfig /renew "Ethernet"
Use these only on a network that intentionally uses automatic IPv4 configuration. Releasing an address interrupts its existing connectivity until another configuration is obtained. If you are controlling the computer through that connection, do not perform the release remotely without a recovery plan. Run the commands with appropriate permissions and use the actual adapter name if it differs.
Inspect the updated configuration with ipconfig again. Did the adapter receive an expected address, a usable gateway and appropriate DNS settings? If automatic address assignment still fails, compare another approved wired device on the same port. There may be a DHCP service problem, an exhausted address pool, an access restriction or a fault between the client and DHCP server.
A static configuration needs a different approach. If a computer has deliberately assigned addresses, do not switch it to automatic settings merely because this guide describes DHCP. Obtain the authorized addresses and prefix from the network administrator. Never invent a static address or copy the address used by another computer; duplicate addresses can interfere with both devices.
Step 8: Review VPN, Proxy, And Security Settings
A VPN may route traffic through a tunnel or deliberately prevent ordinary internet access when its secure connection fails. A proxy may direct browser traffic through a service that is unavailable. These behaviors can make a working Ethernet link appear to have no internet. The issue may begin after changing networks, connecting to a work service or installing an application.
If you control the computer and your policy allows it, inspect the active VPN state. Use the VPN’s normal supported reconnect procedure. Do not defeat an organization-required kill switch or remove a managed security product just to test a public website. Contact the administrator when the tunnel is required for ordinary access.
Review proxy configuration under Network & internet in Windows Settings. Browser extensions and individual applications may also apply their own proxy settings. Do not remove a corporate proxy or custom configuration without understanding its purpose. Compare the failing application’s behavior with another approved application if possible.
Windows Firewall and endpoint security tools can apply restrictions to specific traffic or interfaces. Investigate the actual policy or event rather than turning off all protection. The firewall explanation and VPN guide describe why a network can be connected while particular communication is unavailable. If a recent change to a trusted security application coincides with the fault, follow its official support instructions.
Step 9: Run Supported Diagnostics And Check Drivers
Windows provides a Network and Internet troubleshooter through its supported help interface, although the exact entry point can differ across releases. Use the troubleshooting option available on your own Windows 11 installation. Review the reported result and any proposed action before making a major configuration change.
If the adapter stopped working after an update or shows an error in Device Manager, inspect the installed driver details and compare them with the computer or adapter manufacturer’s support information. Obtain the correct network driver for the exact model and supported Windows version. Avoid unofficial driver bundles that may install incompatible software or unrelated applications.
If a supported rollback option is available and a specific driver update clearly coincides with the fault, consider the manufacturer’s instructions for using it. Do not remove the current driver until you have a usable recovery method. On a computer without internet access, download the approved installer using another trusted computer and transfer it safely.
Microsoft describes driver reinstallation as a later troubleshooting option and recommends obtaining a backup driver first. An automatic reinstall is not guaranteed in every situation, especially when the machine cannot reach update services. Follow our safe driver acquisition guide before performing removal. If the Ethernet device is part of a managed PC, request help rather than making changes to required software.
Step 10: Investigate Managed Networks And VLANs
A port on a managed switch can establish a physical link while placing the client in a restricted network segment. Some workplaces also require 802.1X authentication, registered devices or a particular security configuration before granting normal access. Moving a PC to a random active port may result in a different network policy.
If you are troubleshooting a business, school or shared building, confirm that the connection point is intended for your device. Report the affected socket number, approximate time and network status to the administrator. Do not change VLAN assignments, bypass authentication or attach personal switching equipment without permission.
A home network can also have guest segments, isolated devices or access restrictions. If a computer is assigned an address but cannot reach a service that another device can access, determine whether the two belong to the same intended network and policy. Consult the router’s documentation rather than disabling network isolation globally.
For background, read what a VLAN is. Segmentation is often a deliberate security or organizational feature. A useful repair restores the access that the device is authorized to have, not unrestricted access to every part of the network.
Step 11: Reserve Stack And Network Resets For Persistent Problems
Certain Windows networking commands can repair damaged or unsuitable configuration, but they are not interchangeable with inspection commands. For example, ipconfig /flushdns clears the local DNS resolver cache. It does not repair a broken cable, assign a new gateway or resolve a provider outage.
Microsoft also documents Winsock and TCP/IP resets as troubleshooting options. Commands such as netsh winsock reset and netsh int ip reset make changes to networking configuration and may require a restart and administrative access. Use them when narrower checks support a local configuration problem, and follow Microsoft’s current guidance rather than copying an unexamined collection of commands from an unknown website.
A full Windows 11 Network reset is more disruptive. It can reinstall network adapters and return settings to defaults, potentially requiring VPN or virtual networking software to be set up again. Known connections may need their profiles reviewed. Save authorized network settings and arrange an alternative connection or local access before proceeding.
Open Settings, Network & internet, Advanced network settings, then Network reset when the supported instructions and your Windows version indicate that option. Read the confirmation and proceed only if narrow diagnostics have failed. Restart when prompted, then inspect the wired connection and test the original application before rebuilding additional configurations. Do not perform a factory reset of the PC or router simply because an isolated Ethernet problem persists.
Step 12: Verify The Repair And Know When To Escalate
A repair is successful when the original task works reliably over the intended Ethernet interface. Recheck the assigned address and gateway, open multiple ordinary destinations, and test any required work application through its approved connection. If Wi-Fi was temporarily disconnected, restore the preferred normal configuration afterward. Check that required security controls remain active.
Write down the action that produced an improvement. If a replacement cable restored connectivity, keep the damaged cable out of service. If the router port was the issue, mark it for appropriate repair rather than allowing another household device to inherit the fault. If the connection only works until the next restart, record that pattern and investigate why settings or hardware state change.
If several wired devices fail on known-good cables while Wi-Fi continues to function, focus on the router’s LAN interfaces or the intervening wired equipment. If every device loses external access, contact the provider with its documented support details. If only one PC fails across more than one compatible network and multiple known-good cables, the issue is more likely local to that computer or its adapter.
When escalating, provide the Windows version, adapter model, approximate start time, observed link state, tests already performed and the result of another device comparison. Do not publish unredacted output containing device identifiers, organizational network details or other sensitive information. A concise diagnostic record reduces repeated work and makes the next support step more useful.
Frequently Asked Questions
Why Does Ethernet Say Connected When Websites Will Not Load?
The physical link can work while address assignment, routing, DNS, security policy or upstream service fails.
Can Wi-Fi Work While Ethernet Is Broken?
Yes, a router can serve wireless clients even when a wired port, cable, adapter or wired network policy has a problem.
Does A 169.254 Address Mean My Cable Is Bad?
No, it can indicate that expected IPv4 DHCP configuration was not obtained. A faulty cable is one possible cause, not the only one.
Should I Set A Static IP Address To Restore Ethernet?
No, unless the network intentionally requires static configuration and you have the approved settings.
Will Flushing DNS Fix Every Ethernet Problem?
No, it only clears the local resolver cache and cannot repair physical links or a missing broadband connection.
Should I Disable Windows Firewall During Troubleshooting?
No, inspect the specific network policy or application issue instead of disabling protection indiscriminately.
When Should I Use Windows Network Reset?
Use it as a later measure when narrower fixes have failed and you understand its effect on adapters, VPNs and network settings.



