"It says connected, but there's no internet." 😩
You check the IP, and it starts with 169.254. Good news: that one number already told you most of the story.
🕵️ What 169.254 actually means
When a Windows PC joins a network, it asks a DHCP server for an IP address, gateway, and DNS servers. If nobody answers, Windows gives itself an APIPA (Automatic Private IP Addressing) address in the 169.254.0.0/16 range.
That address can't reach the internet or your company network. So the real question isn't "why is Wi-Fi broken?" It's "why didn't DHCP answer?"
1️⃣ Confirm it
Open Command Prompt and run:
ipconfig /all
Look at the active adapter:
-
IPv4 Address starts with
169.254👉 no DHCP lease - Default Gateway is blank 👉 same story
- DHCP Enabled: Yes 👉 it tried and failed
In PowerShell you can get a clean view too:
Get-NetIPConfiguration
2️⃣ Ask for a lease again
Sometimes the request just timed out. Try again:
ipconfig /release
ipconfig /renew
If /renew hangs and fails, check the physical stuff:
- 🔌 Is the cable seated? Try another port or cable.
- 🖥️ On a dock? Unplug and replug it, or test without the dock.
- 📶 On Wi-Fi? Forget the network and reconnect.
3️⃣ Zoom out: one PC or everyone?
This is the question that saves the most time. ⏱️
- Only this PC: suspect the adapter, driver, switch port, or a disabled network card. Try another device on the same jack or Wi-Fi.
- Several people in the same area: suspect the network side, like the DHCP server being down or the scope running out of addresses.
If it's the network side, escalate with the details: location, how many users, time it started, and that clients are getting 169.254 addresses. That turns a vague "internet is down" into a ticket the network team can act on fast. 📋
⚡ The takeaway
Don't jump straight to reinstalling drivers or resetting the network stack. A 169.254 address tells you exactly where to look: the DHCP conversation.
What's your first check on a "connected, no internet" ticket? 👇
Top comments (0)