Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Macbook Self Assigned IP address connection problem

Hi everyone

I bought an MBP in December 2011, 13'' running MACOSX10.6.6

I have very stable connections at home and various locations including public WiFi connections, hotels etc but cannot get a connection to my Work's WiFi.

At work we have several wireless access points which are linked to our buildings server, however when I try to connect my Macbook to the network the airport bar says it has a self assigned IP address and cannot connect to the internet. We have reset the wireless routers at work, and other devices manage to interact with the network and connect to the internet no problem.. just the Macbook won't connect.

To try and fix I have tried renewind the DHCP lease however it has no effect on the problem.

Any suggestions anyone?

Message was edited by: andy.burland

MacBook Pro, Mac OS X (10.6.6)

Posted on Feb 1, 2011 12:27 PM

Reply
61 replies

Apr 12, 2011 9:19 AM in response to andy.burland

I bought my Macbook Dec 2010. When I got my computer back from Apple Care, my network settings were lost. As a result, I am having this issue.

My setup is a Macbook Pro with Leopard 10.6.6. I do not use a firewall.
At home I have an Airport Express network which I can still access perfectly.
But when perfoming the installation of University wireless, I merely get full connection without access to the Internet due to a 'self assigned ip' starting with 169.xxx.
I have perfomed the installation meticulously, and I've mimiced all the settings on my old Macbook running on an earlier Leopard version.

It feels like I have tried every trick in the book (... mac forums that is.)
I am getting so desperate. I really need some assistence with this seeing how the university is my primary work station, and the University support is totally clueless.

I've read "reinstall Leopard". Has that worked for anyone out there?

Apr 28, 2011 10:53 AM in response to andy.burland

I have the reverse problem. My new macbook pro can connect to the wifi at work, but gives the "self assigned IP" message at home.


The router at home has WEP security and is a Westell router/modem from FiOS. It's not the router, because I have an older Dell Laptop running XP that connects with no problem. My brother and sister in law, both have older MacBooks and also have no problem connecting.


I've only had this MacBook for less than a week and never thought I'd be having this type of "windows" like difficulty. Does Apple acknowledge that there is something broken? I've seen hundreds of messages about this same issue going back more than two years.


I've yet to see any fix suggested that works for me. Plugging directly into my house network or into the router/modem itself works fine.

Apr 28, 2011 12:58 PM in response to Alexmontreal

I HAVE FOUND THE CURE!


By inspecting my colleague's macbook pros (which were working fine on the network), I found this difference in configuration:


Under preferences, airport, click "advanced"

Under the tab 802.1x, select the desired wifi network in the box on the left

Type your username and password

Then in the protocol box, I unchecked the first box "TLS" and left the three others checked ("PEAP", "TTLS" and "EAP-FAST")


I then retried to connect to the network and it worked, stating that I was connected via PEAP. The IP adress changed, meaning that it was assigned by the network.


Hope this helps.


It may not resolve everyone's issues, but it gives an idea on where to look (protocols)


I'm happy:-)

Apr 28, 2011 1:00 PM in response to andy.burland

I HAVE FOUND THE CURE!


By inspecting my colleague's macbook pros (which were working fine on the network), I found this difference in configuration:


Under preferences, airport, click "advanced"

Under the tab 802.1x, select the desired wifi network in the box on the left

Type your username and password

Then in the protocol box, I unchecked the first box "TLS" and left the three others checked ("PEAP", "TTLS" and "EAP-FAST")


I then retried to connect to the network and it worked, stating that I was connected via PEAP. The IP adress changed, meaning that it was assigned by the network.


Hope this helps.


It may not resolve everyone's issues, but it gives an idea on where to look (protocols)


I'm happy:-)

Apr 28, 2011 6:12 PM in response to Alexmontreal

My configuration doesn't have anything on the 802.1x tab. It appears that it only applies if you have something other than WEP security.


I wish I knew why it is only the Mac that has issues. I tried manually assigning IP and DNS numbers, which did away with the self assigned IP issue, but the DNS lookup fails and I can't ping anything, let alone get anywhere online.


Plugging into the network with a cable works fine, the DHCP assigns everything as it is supposed to. I tried all the stuff online I saw to try and fix the WiFi, none of which helped.


Glad you solved your problem. It gives hope.

Jul 6, 2011 3:39 PM in response to andy.burland

This is an extremely annoying problem. I have had it off and on for for than a year. For the most part it happens only on my MBA. Then OS is currently up to date with 10.8.6, but the problem also happens in prior OS versions. For the last few weeks my iPhone, iPad 2 and MBP have app been able to connect at Panera in Cupertino, but my MBA has not. Then same was true on several recent business trips, but I did not have the MBP with me. The Air does connect normally to most networks, but some give it this self assigned IP of 169.xxx.


It has happened at home to me on both the Air and iPad 2, in both cases rebooting the router worked, though on the Air it took several reboots.


With the air being unreliable, I am forced to travel with the MBP, which is not ideal as it is my personal main machine for home.


There are many threads on this topic dating back several years, but i have yet to find a real solution.

Jul 7, 2011 11:21 PM in response to andy.burland

Here is my solution to the self assigned ip adress problem.

Before doing this make sure you have the network password saved somewhere as you will need to renter the password to setup

Fist step go to network preference pane and in the preference pane do the steps below

Turn airport of

Got to advanced and select the network that you are having problems with and click on he minus sign to delete that network

click on ok and then apply

Second step go to key chain access and delete the password for the network you just deleted in he preference pane

Third step turn airport back on and select the network again and renter the password

I hope this works it works for me on wep

Jul 11, 2011 1:28 PM in response to Alexmontreal

Under preferences, airport, click "advanced"

Under the tab 802.1x, select the desired wifi network in the box on the left

Type your username and password

Then in the protocol box, I unchecked the first box "TLS" and left the three others checked ("PEAP", "TTLS" and "EAP-FAST")


This really works. At least it solves my problem. Before unchecking "TLS", the self-assigned IP address is 169.254.*.* (default IP). After unchecking "TLS", the assigned IP is our intra-system IP address (10.*.*.*). This is why it works.

Aug 17, 2011 11:57 AM in response to sebaaaa

i had hope there for a minute. but there is nothing there under that 802.1x tab, so i can't use this info. i am using a router with WEP. just to provide additional info, it's my airport which can't connect, it shows that it is connected to the network but not the internet due to the self-assigned IP, though actually the other mac on my network can no longer see the macbook pro and vice versa. i changed to set DHCP manually but it still, after a bit, resets its IP to the self-assigned bad one. this happened, as i've seen it did to others, after i'd traveled with the laptop and used a couple of different networks, then returned home to this problem. please anyone who like me does not have a network to change under 802.1x, share if you've found a solution. i'm pretty desperate.

Nov 13, 2011 3:01 PM in response to cynthiafromweehawken

I found i had the same thing. Nothing under the 802.1x tab however the bit about turning off your wifi and removing the passwords from the keychain by **sebgod** actually worked. But i didnt just remove the passwords. I searched under the "keychain Access" app and deleted everything that had my wifi in its title (of course i checked how it was linked to be sure) but when i turned my wifi back on i connected with ease.

Nov 19, 2011 12:35 AM in response to ZainfromSF

I was having the same problem with the wifi not connecting to our home network on only one of our Macbooks. It kept giving itself a self assigned ip address. Everything else would connect fine to the home network and the computer with the problem connected fine to every other network aside from our home wifi. After reading this thread and trying everything on it, this is what finally fixed it: I didn't have anything under the 802.1x tab either. So I:


Turned the Airport off and completely deleted the Airport in network preferences.


Then I went to keychain access and deleted EVERY wifi network password saved under both Login and System.


I turned the computer off and removed the battery and did the SMC reset by holding down the power button for 5 seconds.


When I restarted the computer, I reset the PRAM by holding down OPTION, COMMAND, P, and R at the same time RIGHT AFTER I pushed the power button to turn it on and before the grey screen appeared.


It reset and when the computer was back on, I added the airport again and joined my home WEP wfi network. It worked perfectly! Now I don't know if all of these steps are required to fix the problem but this is what worked for me. The Macbook with the problem was a black Macbook running 10.6.8. Good luck!

Macbook Self Assigned IP address connection problem

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.