Ask Leo!

Why can't I connect with a 169.254.x.x IP address?

Home » Networking » Network IP Addressing

Summary: 169.254.x.x IP addresses are self-assigned when your computer can't get an address any other way. It's an almost sure sign of a problem.

My IP address was 192.168.x.xx, and somehow it was changed to 169.254.xx.xx. Because of this I can't access the internet. Any ideas?

Your IP address wasn't "changed" so much as it was broken.

If you end up with an IP in the 169.254.x.x address range, then something is definitely wrong.

For most folks, the IP address of your computer is assigned when you boot your machine. Using DHCP, your computer asks for an IP address, and a DHCP server responds by assigning one:

Simple DHCP assignment

If you're behind a NAT router it'll be the one handing out IP addresses and you'll most commonly get an address in the 192.168.x.x range. If you're directly connected to the internet your IP address could be almost anything. Exactly what range it'll be in is defined by which IP address ranges have been assigned to your ISP.

169.254.x.x, however, is special.

Consider: what happens when your computer asks for an IP address and no one responds? Due to a network problem, or maybe not being on a network at all, perhaps there's no DHCP server to hand out IP addresses.

What happens is this: your machine waits for a while and then gives up. But when it gives up it invokes Automatic Private IP Addressing, or APIPA, and makes up its own IP address. And those "made up" IP addresses are in the 169.254.x.x range.

"It's like having an unlisted phone number that's so unlisted that even the phone company doesn't know it."

Now, a 169.254.x.x IP address is pretty close to useless. The reason that IP addresses are assigned is so that the upstream networking equipment knows where to send or how to route packets that are destined to reach a machine at a particular address. In other words, when things work that equipment knows that your machine has this address. If your machine makes up its own address, no one else knows. As a result, there's no way to know how to get to your machine.

It's like having an unlisted phone number that's so unlisted that even the phone company doesn't know it. No one can call you.

Even connecting "out" to visit, say, a web site or other server doesn't work because there's no way to know where to send the response.

In fact, the only utility I've ever found with a 169.254.x.x address is if machines are connected directly to each other, then some protocols can be made to work machine-to-machine using the IP addresses. Most, however, do not.

It's frustrating enough that I consider a 169.254.x.x the same as "it's broken" and move on to resolving the underlying cause.

About all you can really say from getting one of those addresses is simply that the machine cannot reach the DHCP server over the network.

  • If you're connected via a NAT router, then either your computer is not actually connected on the network to that router, or the router itself isn't responding to the DHCP request. I typically triple-check my cabling, and perhaps reboot the router.

  • If you're connected to the internet directly then there's something about that that isn't working. Check the cabling to your broadband modem, and check the cabling from your broadband modem to your telephone or cable line. And, if all else fails, call your ISP - it may be their DHCP server or some other item they control that's at fault.

Bottom line: if you're getting a 169.254.x.x IP address then something about your network setup isn't working, and you probably want to investigate what and why.

Related:

Article 11677 | Posted July 18, 2007

Recent Comments
0 Comments

Tobie, try new port on router? new cable? diffrent computer, connected to the router hardwired? Reset your router? manually configure your ip on that comptuer? Run->CMD->ipconfig /release (Enter) ipconfig /renew (Enter)? 30 sec power cycle? Finally Baseball bat, bet u could hit a home run!!!!

Posted by: EdVpNb at July 24, 2007 10:16 PM

ahhh, the baseball bat.. The first and final solution to all your problems :)

btw, I am my home... 127.0.0.1

Posted by: Chris at July 31, 2007 2:59 AM

The one an only home i have is "::1"

Posted by: Ex at August 22, 2007 6:58 AM

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ex, you're ahead of your time. To bad your home isn't widely available yet.

Someday.

Leo


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFGzKDGCMEe9B/8oqERAkPBAJ9XgWdx1IT9GCf6tFs9UWtEkw9gBgCggOSw
PhS+NrTmugnCMTyYhctjMn4=
=uU2Z
-----END PGP SIGNATURE-----

Posted by: Leo A. Notenboom at August 22, 2007 1:46 PM

I have the same problem and I am desperate in getting this resolved once for all.. Can you please help? Thanks.. I am running windows xp and its my home laptop. Thx

Posted by: teemu at September 13, 2007 3:47 PM

hi, i wanted to know why i am receiveing a message like this (the server name or address could not be resolved) . this happens when i try and conncet with just 1 website , ultimate baseball online, everything else works , it doesnt make any sence to me. please help me . thannk you

Posted by: chuck stewart at September 25, 2007 5:52 PM

I had the same problem with this wrong 169.254 ip address. Please check if you have set up WEP. If yes, check the authentication type; it must be "Open Authentication" on your wireless PC, otherwise the router can't send the right ip address acording to the DHCP range, and the PC assumes the 169.254 managed by APIPA. It's possible also to set up static IP address, but is not a good solution, and the conection is also very unstable.good look

Posted by: Carlos Eduardo at January 18, 2008 10:51 AM

how do i get a new ip address so i can play xbox 360 live?

Posted by: Austin Whipple at January 27, 2008 11:39 AM

I seem to have found a solution to ip address 169.254.x.x following guidelines by leo.
I simply went to services in administrative tools,right clicked on DHCP client stopped,waited for 5 secs and restarted DHCP client,unplugged ethernet cable from pc,restarted pc and router.
Turned on the router first and plugged in the ethernet cable back in as pc started again.
Checked ip address and pc picked up the right ip address letting me reconfigure the router.

Posted by: rajiv sampat at March 27, 2008 6:38 AM

who said WEP? DON'T USE IT!!!!! Use WPA (WiFi Protected Access). it's MUCH more secure.

Posted by: herman greenstein at May 26, 2008 3:09 PM

Post a comment on "Why can't I connect with a 169.254.x.x IP address?":






(Email Address will not be published.)

Remember Me?

By popular demand...
my tip jar
Cuppa Joe
Buy Leo a Latte!

(you may use HTML tags for style)

New!

RSS feed Subscribe to the RSS Feed specifically for comments on this article.

Before commenting, please...

Please wait. Your comment is being processed ...


Ask Your Question:


ask-leo.com
Web

Stay Informed

Weekly Newsletter

Archives

By Category
By Date

Advertisers

Advertise on Ask Leo!

««   »»

Question? - Ask Leo!
Who is Leo?
Link to Leo!

Terms, Conditions & Privacy