Self assigned IP address

After hour and hours of trying a fix.

I Factory reset my router and now all works fine ! Do this it works.

Thank you so much Desigurl03! I also couldn't connect to my home wi-fi (although my son's mac worked fine, as well as, my ipad). I tried every method before yours and none of them worked. After days without internet on my laptop, your solution worked for me. Two thumbs up!

Ok, so my problem migrated from a self-assigned ip issue into something else. For me, I think it was a keychain issue because after deleting the keychain entries and reconnecting it now "connects" fine. However, now it thinks I am completely connected (green dot) but I can't actually access the Internet (browsers think DNS issue).

I have tried everything above, I get the same issue with manually assigned ip. Must be a communication issue with the router, I think, but unfortunately I don't have the luxury of resetting the router to factory or changing the wep to wpa. My iPhone and iPad connect perfectly fine, and my MacBook Air used to be perfectly fine on this network before.

Dying here... Help!

(btw, where is apple support on this?)

I also had this problem for both ethernet and wifi connections,

with Wind*ws in Bootcamp mode working,

and all other devices and/or colleagues at work connecting,

and most solutions didn't work.

What solved it for me (I hope it lasts) after 3-4 stressful days was

a 'Repair Disk Permissions' through the Disk Utility.

It found that the 'com.alf.plist' permissions caused the problem.

So maybe you don't need to delete it, at least in some cases.

(Apple Support will be 19$ -in my region at least!)

I did 'Repair File Permissions' followed by a Restart, and it worked!

Cheers!

After spending hours trying to resolve the same problem of not being able to connect to the internet - also got: "the Wi-Fi has the self-assigned IP address 169.254.222.165 and will not be able to connect to the Internet."

ericdy's solution sorted out my problem. I think he needs to replace some of those how ranking advisors on this forum!

Woo hoo, glad it was helpful, can't take the credit though because I found the solution through others. I just remember how frustrating it was trying to get to the bottom of it. I haven't had another problem with it since I applied the solution many months ago. All the best!

Do this the stuff you find at the bottom of this thread:

https://discussions.apple.com/thread/3864270?tstart=0

I found a work-around that works for me where none of the other solutions posted before have worked (for me). The beauty of this fix is that it works when you are using wifi away from home (e.g. in a coffee shop or hotel) and can't set a static IP because you don't know what numbers the router is using.

Turn on the AirPort, select the network, let it connect. Go to System Preferences -> Network, select your Airport connection then click Advanced, and select the TCP/IP tab. You will see the self-assigned IP address.

Turn your Airport OFF (right click or control click on the icon in the menu bar, select Turn AirPort Off).

In the still-open Advanced settings TCP/IP window, click on Renew DHCP Lease. Do this several times, as it may "renew" with the self-assigned IP address the first few times. Eventually you will get NO IP address. This means you have finally convinced the buggy DHCP process to abandon what it thinks it knows about an IP address you have previously "used" (the useless self-assigned IP address).

Now turn your AirPort back on (right click or control click on the icon in the menu bar, select Turn AirPort On). Let it come on, and connect (or offer to connect) you to your wifi. If necessary, select the wifi you want to connect to.

Watch in the still-open Advanced settings TCP/IP window as your connection gets an IP address. Sometimes it briefly shows the self-assigned address before getting a routable address. When you have a working network connection you need to click "cancel" to close the Advanced settings window and return to the Network settings window, from there you can just close System Preferences.

I have found this to work 100% of the time where none of the other fixes in this thread helped me.

Oops, please ignore. (No way to delete after posting. grrr.)

I've tried everything I found online and nothing worked. Then I tried something that finally fixed my wifi after months of trying. Here's the link for the video I made showing what to do (very easy!)

http://www.youtube.com/watch?v=DHCBRsSvFwA

Hopes this helps. I was extremely happy when it worked for me.

Of all the (increasingly common) bad things wrought by Apple software and firmware updates, this one should win an award.

I tried everything in this thread -- not necessarily in the order I found them -- and one finally worked for me. I report this for the Apple engineers that I'm sure are working tirelessly on this problem even as I write ;-]

First the basics: MBP late 2007. 10.8.2. Wireless router is an Actiontec supplied by Bell Aliant in Atlantic Canada. I installed 10.8.2 about 10 days ago. The MBP is set to "Never Sleep" and I am quite sure I had not done a restart since installing 10.8.2. No problems at all until this morning. This morning, the dreaded self-assigned IP address was waiting for me. All the other devices in the house were still connecting over wi-fi, no problem.

The trick that eventually worked for me was this: 1) shut down 2) connect ethernet cable directly to router 3) power on computer. Please note that I left wi-fi on throughout this process. Wi-fi and ethernet were both immediately connected and both assigned valid IP addresses from the router. I disconnected the ethernet, and the wireless continued to work. I put the computer to sleep, woke it up, and wi-fi is still working. Will update if it stops working again.

It is just so wrong that we've all had to waste time on this. Good luck to everyone.

A sad update to my last: when I physically closed the MBP (as opposed to just putting it to sleep) I lost the wi-fi again. I was able to get it working again by simply opening it and plugging the ethernet cable in again, but every time I close it, it loses the connection again. Weird.

Ian, did you try the solution I posted above? Open your network settings, go to the TCP/IP tab for your wifi connection. Then in the toolbar at the top of your screen, turn wifi off. Then in the TCP/IP tab click "refresh DHCP" until it refreshes to empty (no IP address, self-assigned or other). Then turn the wifi back on using the toolbar icon, and select your network (if necessary). If you do this, does it come back up with a self-assigned IP or does it give you a routable IP?

Actually, this was one of the first things I tried! The solution sounded almost as weird as the problem, so I thought why not?

Didn't work for me. Tried it twice.

Also, an update: I tried ethernet on a non-wireless router within range of the existing wireless signal. This did not bring the wi-fi back.