I tried many different combinations the so called power cycle, re-creating wireless network interfaces, trashing the plists and network config files and nothing worked for me. Then I got the idea of reseting my Time Capsule configuration and it worked and pushed me into party mode.
Open Airport Utility 3. Create a new wireless network with a different sid 4. Set up password…. From your Mac or other devices, select the newly created wireless sid. You are a genius!
Saved me a bunch of trouble cause I was messing around with my router, and somehow got to the original problem. Keep being awesome! My husband will be very happy tomorrow am!!! Simple solution!!! I take that back!! I have a MacBook Pro with Tried the process and other tricks discussed on the web and none worked. At the end, I tried to turn off WEP authorization of the wireless router.
The macbook finally was able to get an IP. I then setup the WPA authorization on the router and no problem either, which is the setup that I am using now. Thank you so much, I have struggled so long searching the apple web site to no avail! Ich bin Ihnen sehr dankbar!! Thank you so much! The only thing that was different for me, was once I completed all the steps, I had to go back and re-enter the original WEP Key instead of my old password.
Fix self-assigned IP addresses in OS X
Otherwise thanks! You saved me a HUGE hassle! Thank you very much! Same problem here and I have struggled so long. Solution may be even simpler! I tried several of the above solutions that seemed less extreme to no avail. One of the above comments got me thinking on those lines where a user mentioned that you cannot get a static IP on some networks.
How To Fix Common Connection Wi-Fi Issue: Self-assigned IP on MacBook | Technobezz
I do not fully understand what all of this means, nor have I tested my ability to connect other computers or my Sony Playstation to the network… but at least Im back online with my primary computer! One thing that I found was my IP range was only set on my Netgear wireless router to support 10 devices from I increased the upper range to None of this has worked. Any and all help is greatly appreciated. Man, I was worried about having to take days to fix this, but the firewall thing totally worked. Thanks a bunch. I found that this can also happen if the IP address that the DHCP server assigns is already in use by another device on the network.
Initial attempts to address the problem include creating new network locations to refresh the network port configurations, or manually refresh the DHCP lease to force a reconfiguration for the port.
While these are good attempts, many times they do not fix the problem. The reason OS X issues self-assigned IP addresses is to allow a network interface to create an ad-hoc network if needed, without the presence of an established network. However, this is only done if the network port detects a proper hardware connection but cannot communicate with the DHCP server to obtain an IP address.
Usually the main culprit for this is configuration problems with the system's firewall. When people perform major configuration changes to their systems, sometimes the settings may not migrate properly.