DEV Community

Bryz︱🦾
Bryz︱🦾

Posted on

"Connected, But No Internet": Check for a 169.254 Address First

#itsupport #windows #networking #beginners

A user calls the help desk: "My Wi-Fi says connected, but nothing loads." Before restarting the router or reinstalling network drivers, spend 30 seconds checking one thing: did the PC actually get an IP address from DHCP?

Step 1: Look at the IP address

Open Command Prompt (no admin rights needed) and run:

ipconfig
Enter fullscreen mode Exit fullscreen mode

Find the adapter the user is on (usually Wireless LAN adapter Wi-Fi or Ethernet adapter Ethernet) and look at the IPv4 Address line.

IPv4 Address. . . . . . . . . . . : 169.254.37.12
Enter fullscreen mode Exit fullscreen mode

Step 2: Know what 169.254 means

An address that starts with 169.254 is an APIPA address (Automatic Private IP Addressing). Windows assigns it to itself when it asks for an address from a DHCP server and gets no answer. The adapter is "up," but it can't reach the router or the internet with that address.

A normal address on most networks looks more like 192.168.x.x, 10.x.x.x, or 172.16.x.x to 172.31.x.x, with a Default Gateway filled in.

Step 3: Ask for a new address

Release the current address and request a fresh one:

ipconfig /release
ipconfig /renew
Enter fullscreen mode Exit fullscreen mode

If /renew succeeds, run ipconfig again and confirm the address no longer starts with 169.254 and a default gateway is listed. Then test:

ping 8.8.8.8
Enter fullscreen mode Exit fullscreen mode

If that ping replies, basic connectivity is back.

Step 4: If it's still 169.254

The PC still can't reach a DHCP server. Narrow it down:

  1. Check the physical link. Reseat the Ethernet cable or forget and rejoin the Wi-Fi network.
  2. Test another device on the same network. If it also fails, the problem is likely the network or the DHCP server, not this PC.
  3. Check for a static address. Run ipconfig /all and look at DHCP Enabled. If it says No, someone set the address manually; follow your org's process before changing it.
  4. Escalate with the ipconfig /all output pasted into the ticket so the network team can see exactly what the PC reported.

Why this habit helps

A 169.254 address points you straight at DHCP or the connection to it, so you skip the guesswork of driver reinstalls and reboots. And when you do escalate, the next tier gets clear evidence instead of "internet is broken."

One command, 30 seconds, and you know whether it's this PC or the network.

Top comments (0)