Ethernet Blinking But No Internet Link Is Fine Fix Upstream
The port blinks happily, Windows may even say 'Connected' - yet no page opens. Stop blaming the cable. A living, blinking link means the local wire is fine; something between your PC and the internet is broken. Here is how to find which hop.
By Technical AnshuWindows 10 / 11Wired Network Fix
Watch the full fix in the video - every step shown live on a real PC
Learn to separate two different failures that people constantly confuse. No link - lights off or flapping - is a physical problem. Link fine, no internet - lights blinking, data clearly flowing somewhere - is an addressing or upstream problem: the PC may have no valid IP address, no working gateway, dead DNS, or a router whose own internet connection has dropped. Each has a different fix, and this page tests them one hop at a time.
ipconfig - reading your address tells you the story
IPv4 Address . . . . . : 169.254.20.41 <- no real address given
Subnet Mask . . . . . : 255.255.0.0
Default Gateway . . . : (blank) <- no way out of the network
A 169.254 address means your PC asked for an address and nobody answered. The cable and port can be perfect - this failure sits at the router, the DHCP service, or a broken network stack on the PC.
Example ipconfig output. A healthy result shows an address like 192.168.1.x with a gateway filled in.
1
Step 1 - Read Your IP Address Before Anything Else
Open Command Prompt and run ipconfig. Three results, three different diseases:
Address like 192.168.x.x or 10.x.x.x, gateway filled in - addressing is fine; the fault is further out (router's internet, DNS). Go to Step 3.
Address starting 169.254, gateway blank - your PC got nothing from DHCP. The link is alive but nobody is handing out addresses. Go to Step 2.
'Media disconnected' - that is not this page's problem; that is no link at all. Use the dead-link ladder instead.
2
Step 2 - The 169.254 Address - Ask Again, Then Look at the Router
Run ipconfig /release then ipconfig /renew. Often the address arrives on the second ask.
Restart the router or switch - a hung DHCP service is a classic cause, and other devices may be coasting on addresses they got earlier.
Check whether other devices are also failing to get addresses. If yes, the router or DHCP server is the fault, full stop.
If only this PC fails, reset its network stack: netsh winsock reset and netsh int ip reset, restart, and test again. Also remove any static IP someone set by hand and return the adapter to automatic addressing while you test.
3
Step 3 - Gateway Answers? Then Test the Internet by Number
With a valid address, walk outward hop by hop:
ping your default gateway (for example ping 192.168.1.1). No reply means the fault is inside your own network - cable run, switch, or the router itself.
Then ping 8.8.8.8. Gateway replied but this fails? Your router's own internet connection is down - check its WAN light and your ISP, not your PC.
Both pings work but websites do not open? That is DNS. Confirm with nslookup google.com. Fix by setting DNS manually on the adapter - for example your router's address, or a public DNS such as 8.8.8.8 - or by restarting the router whose DNS relay has hung.
This three-ping sequence isolates the broken hop in under a minute. Never skip it and start reinstalling things at random.
4
Step 4 - The Traps That Imitate an Upstream Fault
Before blaming the ISP, rule out the local impostors:
Proxy settings: check Settings for a manual proxy left behind by old office software or removed by nobody - a dead proxy blocks every page while pings succeed.
Antivirus or firewall software: temporarily the prime suspect when the failure began right after its update. Its own logs usually admit the block.
Captive portals: in hotels, colleges and some offices the first page must be a login page. Open a plain-HTTP site to trigger it.
One device banned or filtered: in managed networks a PC can be blocked by MAC filtering while everything else works - if every test fails only for this machine on a network you do not administer, ask the administrator.
Watch the Complete Fix in the Video
See the adapter settings changed live, step by step, in the full Technical Anshu video.
Windows says Connected but no website opens. Where do I start?
With ipconfig. A 169.254 address means DHCP failed - renew the address and check the router. A normal address means test gateway, then 8.8.8.8, then DNS with nslookup. The answers point at the exact broken hop.
Why can I ping 8.8.8.8 but not open any website?
That combination almost always means DNS is broken: your PC can reach the internet by number but cannot translate names into numbers. Set a working DNS server on the adapter or restart the router, then test again.
Other devices have internet on the same network. Is it my PC then?
Very likely. Focus on this machine: renew the address, remove any hand-set static IP or proxy, reset the network stack, and check security software. If the address is valid and only this PC fails at the gateway, also try a different switch port to rule out port-level filtering.
This guide is based on the Technical Anshu video on fixing a blinking Ethernet adapter. Stuck on a step? Ask in the video comments - that is where help reaches fastest.