IP address of 169.254.x.x = no internet connection

I've had a torrid time with TimeWarner most of the day to discover that my Airport Extreme has suddenly defaulted to an IP of 169.254.x.x address. In other words, I can't connect to the internet at all using wireless, since addresses of 169.254.~ are invalid IP addresses.
However, if I connect my laptop via ethernet, I can connect no problem. I've tried: flushing the DNS Cache using Terminal... no luck. The only thing that will get me on the net is to connect my laptop directly.
Not ideal, since I have two other iMacs in the house in other rooms.
Can anyone help me with a solution to this dilemma? Much appreciated... help!

Hey, thanks... that definitely helps. Pain in the ***, but it's good to know.
I eventually got my 2-year-old Extreme replaced with a brand new unit at a nice Apple Store on Long Island, who gave me just the new unit from the box and the power supply. However, although my network now works again, the utility keeps telling me I need the latest Airport Utility (version 5.5, I believe).
I only have version 5.4.2. Apple's download site doesn't show 5.5, or is this an error message?

Similar Messages

169.254 ip range and internet connection

Hi,
I've got a iMac connected to a windows network.
The IP Range for this network is 169.254.92.x. (it's an historical setup, and i can't change it, due to all the PCs and windows servers...).
The imac can connect to internet via the router for a little time, but after some minutes, all the internet connections (mail, safari) stop working.
But, Internet Explorer in Parrallels Desktop is running well, which means that the network works fine.
Does Leopard don't work when it's network setup is set to a 169.254.X.X ip range?
Thanks for your answers (and sorry for my english )
Bertrand.

Bertrand POURCEL wrote:
Yes, all the network settings are done manually.
And no, it's not possible to install a new router with DHCP. There's 50 PCs and 3 Windows Servers over the network
It takes less than 30 seconds to update a Windows machine's IP from fixed to DHCP, and perhaps a minute to either reserve an IP or to set the DHCP pool to exclude certain IPs and then to set those IPs as fixed on the servers. You could be up and running using DHCP in under a half hour. The odds are excellent that you have already spent more time than that dealing with the current problem.
If you're running Vista, the steps are:
1 open Network and Sharing Center
2 click on 'View Status' of your network connection
3 click on 'Properties'
4 dismiss UAC pop-up
5 double-click on 'Internet Protocol Version 4 (TCP/IPv4) Properties'
6 click on the 'Obtain an IP address automatically' radio button
7 click OK
You're done.
If you're running XP, the steps are:
1 open Control Panels
2 double-click Network Connections
3 right-click Local Area Connection and select 'Properties'
4 double-click 'Internet Protocol (TCP/IP)'
5 click on the 'Obtain an IP address automatically' radio button
6 click OK
you're done.
Doing this 53 times may be tedious, but will not take a significant amount of time.
Most routers from Belkin, Netgear, Linksys, and Apple will allow you to reserve an IP for a specific machine. Required steps are:
1 get the MAC address of the machine in question, either from the command line or the status dialog; see above to see how to get to the status dialog. You can get the MAC address while setting up DHCP.
2 launch the router control HTML page (or, in the case of Apple, AirPort Utility) and go to the section of the admin page which sets reservations.
3 enter the MAC address for the desired machine. The system will reserve a particular IP just for that machine. It will never be handed out to any other machine.
4 reboot the router
you're done.
The only machines which need reserved IPs are the servers and the printers, so you need do this only for the three servers plus whatever printers you have.
Let me be explicit: if you keep using APIPA for your network range, you will continue to have problems. You can continue using APIPA for something it was not intended for, and continue having to patch things after the fact, or you can move to one of the private network ranges (probably a Class C, as you only have 53 nodes, not counting printers) and eliminate the problem at the source. If you insist on using APIPA, you will have to update the NAT, DNS, and DHCP lists yourself, on each new machine added to the network. And you will not know when there's a network connectivity problem as you will have fixed IPs which show an APIPA address as a normal setting, instead of DHCP-set IPs which show an APIPA address only when there is a problem.
It's your choice. I'd spend the half-hour, but that's me.

IP address 169.254....

Hello,
A few weeks ago, both my ethernet and my airport were working fine in my dormitory and anywhere I went. Then in my dormitory, the ethernet suddenly stopped working as I was using it. I didn't change any settings, I was not messing arround with anything. It just suddenly stopped! I tried asking for help to the people in the dormitory, but being in a place where no one (in the dormitories and IT technicians) really speaks my language and I don't really speak theirs, doesn't help very much. Plus the fact that they don't really seem to be able to use and fix mac problems. My ethernet cable connection works excllent with any other computer that is connected to it BUT with mine.
Anyways, everything is on automatic the way it should be, but it shows that the self assigned IP address is of 169.254. etc, and it cannot connect to the internet. It happens with both ethernet and airport. With the airport I used to connect perfectly, but now, a few places where I used to connect perfectly won't work anymore, and it shows this same IP address of 169.254.blah.blah. It has been driving me crazy not being able to connect to the internet propperly since it is the only way I can communicate with my family. Could anyone PLEASE help me? I am really desperate here T^T Thank You!!
Regards,
Omar.

Try removing all the RAM and putting in new RAM. We had a PowerMac G5 at work that couldn't connect to the Ethernet no matter what we did. I was convinced it was the motherboard/Ethernet connection failure. But after running a couple of hardware tests, it came up with bad RAM. Put in all new RAM, and lo and behold, we have Internet!!
This would explain why multiple computers can connect to an internet connection, but one computer doesn't.
I'm having this problem with my MacBook Pro right now, and will attempt to take out the RAM when I get home to see if it fixes it. I had it at work, and was in the middle of surfing on our Ethernet network, when it suddenly stopped. I just put new RAM in a few weeks ago, so one might have failed.

IP address 169.254 or no IP Address

I have a Linksys WRK54G (model with one antenna). I have problem with IP address.
If I enter with DHCP on the adapter, it receives an IP address like 169.254, which is not accepted by the Linksys. If I enter with static IP address the connection is very instable, some times I have to disconnect the USB adapter and connect again, or even disconnect the power of the router, to get an access to Internet. That means the IP address on the adapter is either wrong or empty. The Firmware Version is 1.55.02, May 21 2004, and I believed that there is not update.
The Radio signal appears as excellent, no surprise because the distance between adapter and router is 5 meters and there is only one conventional wall.
I have tried all of the above:
- uninstall and install the router configuration
- enter with WEP with open authentication, and work also without WEP
- change the channel to 11, the beacon interval, RTS, etc.
I did not try to disable the APIPA.I believe the newtork shoud work properly with this as usually (Am I wrong?).
The problem affects not only desktop PCs with wifi adapter but also LapTop with integrated wifi.
I see that many users have the same problem with different Routers of Linksys.
I would appreciate any assistance anyone may offer. Thank you in advance for your time.

only your wirless computer with the adapter cannot get an ip address?or all of the wireless computers?
if your router has a working computer wired then it must connect wirelessly as well.is your wireless adapter linksys as well?
try to update the drivers for your adapter and try to check if other wireless computers also can't grab an ip from your router.. then if not there is really something wrong with the wireless settings of the router

Why does my WRT54g sometimes give me a 169.254 address???

I have a WRT54G with firmware v1.01.0, Sep. 14, 2006. I've got an Apple G5 attached to it through one of the hardwired ethernet ports, connecting via DHCP. Once in a while, I'll get an address like 169.254.236.186 and can't connect. I have another Mac attached through a linksys wireless to ethernet bridge, and that one gets this kind of address all the time, needing to "renew DHCP lease" every couple of hours, to get a normal 192.168 address back. Can someone tell me how to fix this? Why does it give out such weird addresses? Mike Levin

When the computer fails or face the problem to get the IP from router automatically, then it will assign 169.254.x.x IP. Check the DHCP setting on wireless router and ensure you assigned big enough DHCP IP range. Also you can take a look on this wireless router configuration help..

169.254.x.x and limited wireless connection

Hi, I'm having some problems with my wireless network. I have a WRT54G router set up and 2 computers that connect to it wirelessly. My new laptop with vista can connect to my router and works well. My pc with xpsp2 does connect to my router but it has an ip address of 169.254.213.2, 255.255.0.0 for subnetmask, and the default gateway is blank.
I set everything up to obtain automatic ip and dns info. I tried the repair icon on my task bar, but an error message comes up saying it couldn't renew the ip address. I tried ipconfig /release and /renew but renews with the same ips.
From my pc, I tried pinging around:
to my router (192.168.1.100) and it worked
to my laptop (192.168.1.101) request got timed out
to website (google.com) and it worked.
From my laptop, I tried pinging:
to my router (192.168.1.100) and it worked
to my pc (169.254.213.2) and it worked
to website (google.com) and it worked
So, I THINK my problem is with my linksys network adapter.
I use a WRT54G router
My USB Network Adapter thats on my pc is a WUSB54G

Your PC with address 169.254.213.2 is not connecting wirelessly to your router. This address indicates a failed connection, and it is generated by the PC itself. If you were connected to the router, your address would be 192.168.1.x
The most likely cause is a computer software firewall problem. Temporarily turn off your computer software firewall, and see if that helps.
If you still have trouble, do the following:
First of all, in the router, give your network a unique SSID. Do not use "linksys". If you are using "linksys" you may be trying to connect to your neighbor's router. Also set "SSID Broadcast" to "enabled". This will help your computer find and lock on to your router's signal.
Also, in the computer, go to your wireless software, and go to "Preferred Networks" (sometimes called "Profiles" ). There are probably a few networks listed. Delete any network named "linksys". Also delete any network that you do not recognize, or that you no longer use. Delete your current network (this will remove any old settings). Reboot computer. Return to "Preferred Networks" and re-enter your current network info (SSID, encryption (if any), and key (if any) ). Then select your current network and make it your default network, and set it to automatic login. You may need to go to "settings" to do this, or you may need to right click on your network and select "Properties" or "settings". Reboot computer. You should connect automatically (within 2 minutes).
If the above does not fix your problem, download and install the latest driver for your wireless card.

Correct IP address from router, no internet connection

I setup a network with four PCs. Three of the PCs are connected directly to the router, and one is connected wirelessly. The three PCs wired in are working just fine, but the wireless one is not. When I first set up the connection, I had an internet connection, and suddenly it stopped, and I have not been able to get it back.
I disconnected and reconnected the wireless connnection, and I couldnt get an IP address. I disabled the firewall, and then I was able to get an address (192.168.1.112), but no internet connection (limited or no connectivity). In testing the connection, I was able to ping to the IP successfully, but in pinging from the bad PC, i was not able to get a response. So i think the adapter is sending signals, but not receiving them from the router, hence no internet.
Is there something simple that I am overlooking? Any ideas??

Sorry, this isn't the answer, but I have the same problem, but with a Mac.
We have an old Sony Vaio, an older Mac Powerbook G4 17", and a new MacBook 15". The Viao and Macbook have no problems but my 17" can only connect to the internet hardwired. Wireless, I can only get to the router, but not past it? What gives?
We have the WRT54GL (fw: 4.30.0), which replaced our old (wireless) BEFSR41 which had an Airport hooked up for wireless. That setup worked great. My 17" is running OS 10.4.7 and has the lastest firmwares.

DHCP Address changes to 169.254.x.x after starting to download image in PE

Our network requires the user to register their computer on the network to obtain network access. This really isn't for security, but for tracking reasons. This registration is done via the web on a temporary private network they get sent to if the dhcp server doesn't recognize the machine. Once registered they can either reboot and renew their IP or just wait till the IP times out which is 2 minutes to gain access to the network with a real IP. The tempoary network runs 2 minute lease times because of the limited number of IPs and the large turnaround we have on this network during peak times. The real network runs 4 hour lease times mainly just because of the large turnaround of computers some buildings have been reduced to 1 hour because at 4 hours we would run out of IPs for the building. We have a class B subnet for real IPs that all clients get with IPv4 we have to play a delicate balancing act to keep from running out. We have in the process of implementing IPv6 which could solve some of these problems.
Back to my problem. When a bare metal computer comes in the tech needs to load the machine. At this point it is on the tempoary network. The tech boots the computer into pe either cd or pxe. Then they register the computer with configmgr and start up the correct task sequence. Even with the 2 minute lease time the client maintains constant connectivity no matter how long the user takes to register the client. You can wait days if you like. Once the task sequence is chosen and it starts to apply the image it will fail. If you push F8 and do an ipconfig it shows a 169.254.x.x ip address. If you try to renew the IP you get An error occurred while renewing interface Local Area Connection : The requested address is not valid in its context. You can release and renew and get a new IP, but at this point the task sequence has failed with error 0x80070035. This is a problem with all model computers even in vmware.
Has anyone experienced this problem? I've seen other post before and the solution was always to bump up the lease time which the network guys won't and probably can't do. It is like the IP will not auto renew while downloading an image. This happens whether you do download as needed by task sequence or access content directly. We are in native mode, but had the same problem in mixed.

We need to be able to image bare metal computers from anywhere on the network so using a dedicated vlan is difficult. The requirement for network registration during the setup process has been a problem for years, but with little resolution between the techs and the network guys.
We are using public ips for clients because many years ago the routing hardware couldn't handle the NAT translations for the large number of clients. The network guys don't have dynamic vlans configured although I think they are working on it right now they just piggyback subnets on interfaces. Also the separate vlan for loading computers would be partially difficults since this has to work any all buildings, but because of potential routing problems they don't put a vlan in more than one building. Each building right now has at least 1 dedicated vlan with a corresponding subnet and router. Most of our core is 10Gb with at least 2Gb-10Gb to each building so bandwith usually isn't a problem. The DHCP server is old, but handleing the work load just fine.
Our environment doesn't 100% match the typical corporation that runs configmgr. We have a primary central support area and then many sub support areas that all do their own thing with special image requirements. There is a need to keep these areas separate, but centralliy manages with minimal administrative overhead. So to handle this we use unknown computer support just to make booting with pxe into PE. I then use tsconfig.ini to call a modified version of the unknownsystem.hta from the configmgr sdk. The tech doing the imaging logs into this screen and selects an image collection (the available list is based on the users rights to the collections), ad ou, custom variable settings, and machine name to add the computer to the system and recieve the appropriate os advertisements without having to add the system manually through the configmgr console.
We are still working on ways to avoid the network registration step or register the computer on behalf of the client, but would still like to figure out this problem.
Thanks,
Sam

How do I get rid of second 169.254.x.x IPv4 address on Windows Server 2008 SP2 x86?

I'm sure this is an obvious one but can't figure it out.
I have a Winserver 2008 Sp2 (x86) DC with a static IP address allocated to its only NIC. It seems to have acquired a second 169.254.x.x address automatically which I can't get rid of and which intermittently causes DNS problems (and possibly other)
problems.
ipconfig results are shown below:
C:\Users\Administrator.STRATIS2>ipconfig /all
Windows IP Configuration
   Host Name . . . . . . . . . . . . : STRATIS-SVR02
   Primary Dns Suffix . . . . . . . : stratis2.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : stratis2.local
Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 XT Network Connection
   Physical Address. . . . . . . . . : 00-0F-1F-67-B8-CE
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.11.128.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   IPv4 Address. . . . . . . . . . . : 169.254.140.227(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 10.11.128.99
   DNS Servers . . . . . . . . . . . : 10.11.128.1
                                       10.10.128.1
   NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 8:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : isatap.{D60B08E6-D119-4CB8-BD18-380B7ED48
771}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 9:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Any ideas as to how this might have happened and how I get rid of it (a simple re-boot doesn't do the job).

OK, I followed Syed's instructions. I noticed that under the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\ there were two AdaptorGUIDs, but only one of them had any parameters.
I created the IPAutoConfigurationEnabled parameter for both these AdaptorGUIDs with a value of 0 as instructed and re-booted.
Here are the registry entries for the two AdaptorGUIDs:
After re-booting I did another ipconfig /all, and the APIPA address is still there! Here's the ipconfig output:
C:\Users\Administrator.STRATIS2>ipconfig /all
Windows IP Configuration
   Host Name . . . . . . . . . . . . : STRATIS-SVR02
   Primary Dns Suffix . . . . . . . : stratis2.local
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : stratis2.local
Ethernet adapter Local Area Connection:
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Intel(R) PRO/1000 XT Network Connection
   Physical Address. . . . . . . . . : 00-0F-1F-67-B8-CE
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.11.128.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   IPv4 Address. . . . . . . . . . . : 169.254.62.149(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 10.11.128.99
   DNS Servers . . . . . . . . . . . : 10.11.128.1
                                       10.10.128.1
   NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 8:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : isatap.{D60B08E6-D119-4CB8-BD18-380B7ED48
771}
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 9:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical Address. . . . . . . . . : 02-00-54-55-4E-01
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
[it's a different APIPA address this time, but I guess it is randomly allocated].
Any further ideas for me?
Thanks
Nigel

ACS 4.2.0 AAA-server-IP-address changing to 169.254.x.x

Hello,
I have ACS 4.2.0.124.15 installed on a windows server 2008.
In the configuration menu : network config > AAA server , the AAA-server-IP-address change to 169.254.x.x each time I disconnect the ethernet interface of the server.
Allthough, the ip adresse in my network connection of the windows-Lan-connection is set to static.
Whe I reconnect the ethernet interface of the server, it stays in 169.154.x.x. And I need to reconfigure the real static adresse each time.
Do you knows this problem. Is it a way to avoid it ?
Michel Misonne

Hello,I have ACS 4.2.0.124.15 installed on a windows server 2008.In
the configuration menu : network config > AAA server , the
AAA-server-IP-address change to 169.254.x.x each time I disconnect the
ethernet interface of the server.Allthough, the ip adresse in my network connection of the windows-Lan-connection is set to static.Whe
I reconnect the ethernet interface of the server, it stays in
169.154.x.x. And I need to reconfigure the real static adresse each
time.Do you knows this problem. Is it a way to avoid it ?Michel Misonne
Hi Michel,
It was issue in ACS 1113 SE Appliance and clear solution for the above is mentioned in the below link
http://www.ciscosystems.com/en/US/products/sw/secursw/ps2086/products_tech_note09186a00808d9199.shtml#stat
HTH
Ganesh.H

Why Windows keep detecting ip address such as 169.254.201.217/16 Both on Windows 8 and Windows 8.1

Why Windows 8 and Windows 8.1 (Even Windows 7) detects ip network address 169.254.201.217/16 on my computer???
I keep getting that most of the time.

Hi
This is my host files.
# Copyright (c) 1993-2009 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
And this is my network files.
# Copyright (c) 1993-1999 Microsoft Corp.
# This file contains network name/network number mappings for
# local networks. Network numbers are recognized in dotted decimal form.
# Format:
# <network name> <network number> [aliases...] [#<comment>]
# For example:
# loopback 127
# campus 284.122.107
# london 284.122.108
loopback 127

TS3798 How do I stop my ethernet connection assigning itself a 169.254. ... address?

How do I stop my ethernet connection assigning itself a 169.254. ... address? My iMac is connected to a wired network. The DCHP server is set to allocate the iMac the address 192.168.1.2 but the iMac seems to over-ride this and allocate a 169.254 address. How do I stop this please?

Shouldn't be a need to use manual.
First try renewing the DHCP lease. In Network preferences, ensure the location in the top drop-down is set to Automatic, then click on advanced -
Then click on 'renew DHCP lease'. It may help to turn of IPv6, too, as some routers can't handle it yet.

HT3466 Airport has self assigned IP address 169.254.153.51 and will not be able to connect to the Internet

Cannot connect to internet wirelessly because I get the message "AirPort has the self-assigned IP address 169.254.153.51 and will not be able to connect to the Internet."

I would recommend that you do the following as a minimum:
Power-down the modem, AirPort base station, and computer(s).
Disconnect the AirPort base station from the Internet broadband modem.
While all of the devices are powered-down, perform a "factory default" reset on the base station. This will get it back to its "out-of-the-box" configuration and make setting it up much easier, especially if you use the "Assist me" process within the AirPort Utility. (ref: Resetting an AirPort Base Station or Time Capsule)
After the base station resets, go ahead and power it back down.
Reconnect the AirPort base station to the Internet broadband modem. For the Extreme and Time Capsule, be sure to connect the cable to the base station's WAN (circle-of-dots) port.
Power-up the modem; wait at least 10-15 minutes to allow it adequate time to initialize.
Power-up the AirPort base station; wait at least 5-10 minutes. Note: The AirPort's status light may continue to flash amber after it has intialized. That is because, there may be some additional configuration items necessary, like setting up wireless security, before the overall setup is completed to get a green status.
Power-up your computer(s).
In this basic configuration, the AirPort base station will broadcast an unsecured wireless network with a Network Name (SSID) of Apple Network NNNNNN. Network clients, connected to the base station either by wire or wireless, should now be able to access the Internet through the ISP's modem. Once Internet connectivity has been verified, you can use the AirPort Utility to configure the base station for wireless security and any other desired options. Please post back your results.

My Airpot/Time capsule will not will not connect. It states " AirPort has the self addressed IP address 169.254.231.99 and will not connect to the internet??????l

Cant' get my AirPort to sync up with internet. I get the message "AirPort has the self addressed IP address 169.254.231.99 and will not connect to the internet. How do I fix? Thanks.

What broadband router do you have?
What model Time Capsule do you have?
If you changed the system over from another router.. have you rebooted the entire network.. particularly a cable modem.. did you power off for at least 20min..
Tell us some info and we can help.

HT1338 my airport is not working getting Wi-Fi has the self-assigned IP address 169.254.5.29 and will not be able to connect to the Internet

my wi fi wont work giving me this Wi-Fi has the self-assigned IP address 169.254.5.29 and will not be able to connect to the Internet whats up with the airport how do i fix it

See this discussion.
Wi-Fi has the self-assigned IP address
Troubleshooting suggestions.
Troubleshooting Wi-Fi issues in OS X
Wireless Connection Problems - Fix
Wireless Connection Problems - Fix (2)
Wireless Connection Problems - Fix (3)
Wireless Connection Problems - Fix (4)
Wireless Diagnostics - About

IP address of 169.254.x.x = no internet connection

Similar Messages

Maybe you are looking for