AirPort - Self assigned IP address - no internet!

[kylehart]

possibly connected despite entering the wrong password

Many thanks to all those who have posted info here.

In my case, I believe the Verizon DSL wireless access point I was using allowed me "connect" with the wrong password, but would not subsequently issue an IP address (thus reverting to self-assigned IP). This sent me down the rat hole of trying all the other remedies listed here related to mac wireless networking (not an issue for me on my MacBook with OS 10.6.8)

It sounds bizarre, I know, but the \!/ and self-assigned IP problems are gone after "forgetting" the current connection/password and entering the correct one. (Forget by removing the entry from Network->Advanced->Airport->Preferred Network).

 

[angied]

My Problem Solved!

I have had the same problem with connectivity and thought it was an Apple issue. However, when I bought my Sony Internet TV, I had the same problem. Our PC's connected with no issues, but the TV, Macbook Pro, iPhones and iPad would not connect after shutting them down/turning them off, without first power cycling the router.

On another forum I found this solution that worked for me, after a YEAR of power cycling the router every day!

Log in to your router configuration. (Mine is Netgear)

Go to: ‘Wireless Settings’ –> ‘Security Options’

Change “WPA-PSK (TKIP)” to “WPA-PSK (TKIP) + WPA2-PSK (AES)”.

Re-enter the exact same password you've been using, to avoid having to change passwords on all your devices.

After making this one small adjustment, my Macbook Pro which was sitting open next to me, immediately connected to the wireless. I checked my iPhone, which also immediately connected. I ran to my TV, turned it on and Yes! Even the TV had an immediate connection. It has been 24 hours since then and I have not had to power cycle the router. I have powered off/on all the devices since then, and each time they are immediately connecting to the router with no issues. (before, if I turned off the TV, I had to power cycle the router to reconnect it to the internet again)

WOOT! I know many of you are having similar problems, some may not be quite the same, but this is a simple fix that I have not seen on this forum yet. It's worth a try!

 

[DrJK]

Got to System Preferences, Security, firewall tab, set to allow all incoming connections, go to the network pane, turn off airport and back on again - let it get an IP from dhcp, apply, then go back to security and turn on your firewall again.

This should work for ethernet too, although instead of a turn on and off of airport, you need to select your ethernet connection, go to advanced, ethernet, renew dhcp lease, then OK and apply.

G>

Thanks for this solution. It worked for me, I was having this self-assigned IP problem with both my airport and ethernet. When I checked my firewall log, it had denied access to a file 'configd'. Occasionally a dialog would ask me if I wanted to allow access to configd, and after choosing yes, things would work. But I wasn't prompted with this dialog most of the time, and seemingly the firewall was blocking it configd; I assume lowering the firewall allows access to this file which contains the IP address info.

 

[Achilles75]

So how about this twist with the Keychain fix...

Brand new MBP running Lion. Having the suspected issue of assigned IP address when my DHCP resets every hour or so. I'm trying the solution of going to Keychain and setting it to "Allow all applications to access" on my network password - and Keychain won't let me save the change. It keeps reverting back to "Confirm before allowing access."

 

[hahnfeld]

It's 2012... same issue still exists

My daughter's Macbook suddenly developed this issue while running OSX 10.6.8. The Access Point is rock solid, several other Macs, iPads, and iPhones connect reliably every day.

I tried many of the suggested fixes to no avail (dumped pref files, no firewall, static IP configs, yadda yadda.) I thought I'd outsmart the issue and just upgrade the machine to Mountain Lion. Amazingly, the upgrade didn't change a thing, the problem persisted. Same OS underpinnings I guess.

Anyways, I also noticed that the machine basically refused to fully "forget" my access point. I tried one of the earlier suggestions of manually "Join(ing) Other Network" - entering and joining the same SSID/AP which I was already faux connected to, entered WEP key, selected "remember this network." - and that solved it for me.

 

[pbeaurline]

Switched to WPA2-Personal

10.6.8 here. After a lot of fooling around, I simply switched encryption from WEP which had worked just fine, to WPA2-Personal. The wireless router is now assigning the proper IP address, and everything works.

Philip