Self-assigned IP address after downloading Mavericks

Last night I downloaded Mavericks on my MacBook Pro and everything was working fine. This afternoon however now System Preferences says I have a Self-Assigned IP. I haven't changed any preferences or done anything different so I'm really confused. I can't connect to Wi-Fi or to the Ethernet cable in my room. Any ideas on how to fix this issue?

I am now having this same issue. I have the issue with my ethernet connection. I am trying to share my internet connection between my MBP and my Xbox 360 and I have this pesky self-assigned ip address. PLEASE HELP!!

Similar Messages

After reading hours on this forum still having self-assigned IP address

I just posted this below on another thread but it kinda is in the wrong subforum. This really is a networking problem:
I have spent about 3-4 hours today already (a Sunday after all) reading just about every thread I could find that mentions this problem (airport choosing a self-assigned IP address and thus not sharing the internet from ethernet connection with the iPhone) on this forum and elsewhere.
Power circuit interruption didn't work
rebooting, resetting, etc all not working
password deletion not working
moving it up or down not working
It worked fine now for months. My set up is a dsl router that connects the internet via ethernet to my iMac and then Airport is supposed to share it via Wifi so my iPhone can use it. As I said, that worked just fine for months now.
Yesterday I upgraded to snow leopard and am now on 10.6.4. It worked still fine yesterday!
Then I shut the system down.
This morning reboot and it just won't work anymore.
Any suggestion mentioned anywhere in this forum which a non-specialist like me understands does not work on my setup. I don't know where to go next or who to even ask for help!
It's so frustrating I obviously need this to work.
Because my iPhone has Daylite touch and needs the server setting to work to connect properly and sync. Daylite only syncs via wifi. That's my work!
Anymore ideas out there?
Message was edited by: BettinaH

Hi,
thanks for offering help! Really appreciated.
I'm not quite sure how that should help? I'm always a bit with resetting things. What can it potentially mess up that is working now? What settings will be affected? There is a list but I'm not sure if there are any current changes.
And in the list it doesn't seem to be directly linked to any networking info.
I've tried a save reboot now but while this is apparently a good idea in any event, it didn't help solve my problem. Still getting a self-assigned IP.
I wonder if getting a new router might solve the problem? Mine is somewhat old. The weird thing is though that it did work for a short while before it stopped doing so. So this can't really be then, can it?
Oh this is so frustrating. I must get my network running again.

Self-assigned IP address issue after upgrade

I do a lot of file transferring from my mac to another pc laptop, so I've got them hooked together with an ethernet cable. I had this issue in the past, where I'd try to connect but my network settings kept saying the "ethernet has a self-assigned IP address and will not be able to connect". The solution I found to fixing this was to open up the Advanced Settings, and change the IPv6 configuration to "Link-local only" and then everything would work perfectly.
I upgraded to Yosemite yesterday, however, and now that solution no longer works. Still getting self-assigned IP. How can I fix this??

I took the following from the Aztech website:
8) Can Aztech HomePlugs work with Apple MACs?
Yes they can, Aztech HomePlugs work with Apple MACs. However, there is a requirement for using the Utility software. The Utility software will only run on Microsoft Windows 98SE / ME/ 2000/ XP/ Vista.
Which contradicts itself, if the Utility is required but only runs on Windows, how does that work on a Mac?

Rebuilding aMacBook 1.83 GHz Intel Core Duo, hard drive failure so rebuilding system. Aircard will not stop self-assigning IP address. Any ideas how to resolve successfully?

Had hard drive failure on MacBook 1.83 GHz Intel Core Duo, so had to rebuild the OS on new drive. Was on Lion 10.7.5 prior to failure, but had to reinstall Snow Leopard 10.6.3 since that was most recent OS on media I had. After finally getting ethernet connection to router working, was able to get to internet and download / upgrade to 10.6.8. I assume I can probably buy the upgrade to Mountain Lion 10.8 from there.
Problem is this, Airport will not stop self-assigning IP address for my wireless connection, and unless I can get wireless back on this laptop, doesn't make a lot of sense to continue the rebuild and reinstall of all the software that was on it prior to HD failure. Only way to my home network and router is ethernet now. Everything else on my network (Apple MacBook Pro laptops, iPhones, desktops, and non-Apple printers and laptops) is hooking up to router wirelessly fine.
Any ideas how to resolve successfully so that the airport will stop self-assigning and allow the router to assign the IP address?

When see the beachball cursor, note the exact time: hour, minute, second.
These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
The title of the Console window should be All Messages. If it isn't, select
          SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar at the top of the screen.
Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Some private information, such as your name, may appear in the log. Anonymize before posting.

Problems using MBP as WiFi router for iPad2 (self-assigned IP address)

H/W& S/W:
MBP 15" (model early 2011), running Snow Leopard,
iPad 2 WiFi only, 64Gb, iOS 4.3.4 (8K2).
Scenario:
I am in a location where there is no WiFi. MBP is connected via Ethernet to a DSL network, and has access to the Internet. I turn on Internet sharing, having set the following:
"Share your connection from" set to "Ethernet" and
"Share computers using Airport" ticked.
Previously, I have then connected the iPad 2 via WiFi with the WiFi network created on the MBP, and succesfully worked from the iPad on the Internet (email, browsing, app downloads, ...).
Problem:
Now, however, the iPad connects to the MBP's WiFi network, but when I attempt to access the Internet, I get such messages on the iPad as "Safari is not connected to the Internet" or "Cannot Get Mail ...".
On investigation, I see that Airport on the MBP is in a YELLOW status: Status On, with the note "Airport has the self-assigned IP address 169.X.y.z, and will not be able to connect to the Internet".
On the iPad, the WiFi network shows the IP address 169.X.a.b (with a subnet mask (255.255.0.0).
I have tried:
1. turning Airport off and on
2. renewing the DHCP lease on the MBP
2. configuring IPv4 address in the MBP manually
3. configuring the IP address manually on the iPad (not expecting anything with this, but ....)
4. fixed Permissions" on the MBP disk (suggested on another support community web site)
But none of these make any difference.
Message was edited by: WKH
forgot to mention: Firewall is disabled on the MBP.

Hello,
I've had the exact same problem on my macbook and it really **** me off ! I tried all of the solutions written in this forum and none worked for me ! I was really starting get mad especially that my macbook is quite new...
And the thing is i have no Apple Store where i live which is a pretty F***g problem so I had to wait for vacations to go to france where I took my macbook for check at the apple store...
I just came back right now and my wifi works till now a least far much better than before...The guy was really nice he checked everything and he tried all the solutions on this forum too..Finally he tried to boot from one of '' apple's '' usb that has suberb booting systems...And it worked so finally he re-installed 10.6.5 as it was '' corrupted '' with wifi bugs ! For that he needed to delete everything on my macbook ! GREAT !
After 15 minutes the installation was done and it started like when you buy a new macbook !
And VOILA the Wifi came back to normal !
Hope this helps...
If you have this problem go and see Apple Store or re-install yourself 10.6.5 !
Thanks !

My ipad recognizes my home network but will not connect to the internet. When I click on AirPort/preferences at the top of the imac screen it says..."AirPort has a self-assigned ip address and may not connect to the internet".How can I change ip address?

My ipad recognizes my home network but will not connect to the internet. When I click on AirPort/preferences at the top of the imac screen it says..."AirPort has a self-assigned ip address and may not connect to the internet". If this is the root of the problem,how can I change ip address?
Ipad will connect no problem to other networks.

First thing you need I think is to get your iMac connected to the Internet.
Shut down your iMac and you iPad. Then power off your router. Wait 30 seconds and power up the router.
After the router indicates that it is connected to the Internet then start up your iMac and see if it connects. If the iMac connects to the Internet then your iPad should too.
If this power up sequence doesn't work you'll have to dig into the router setup to make sure it is working properly.

Lost wireless and repeated self assigned IP address

After I updated to OSX 10.5.6 my powerbook started dropping my wireless/internet connection, and adopted a self-assigned IP address. This happened whether I connected to the router via wireless or cable.
I was eventually able to change the system configuration files as suggested in previous posts, and reset my PRMU. This has worked for a wee while, but sometimes on starting up my laptop, the machine self assigns again.
I know the internet is available as I can access it from my iphone.
Then 20min ago, whilst surfing, the internet went down AGAIN, and self-assigned its favourite IP address.
I recently updated to 10.5.7, but the problem remains.
Is this a new problem or has it been going on for a while?
Also, is it a hardware or a software problem?
Any ideas?
Charlie

If you are able to connect initially and then it drops out I would look towards possible sources of interference. While most modern devices avoid this issue fairly well, it is a possibility. Devices such as cordless phones used to cause problems.
If it is dropping out while you are physically connected, I would perhaps check the settings on your router. Most models have a reset function which will allow you to reset it to factory defaults. Then you could reconfigure it and see if the problem persists.
The other possibility is that there is a software service on your macbook that is starting up and causing the network loss. If possible, I would attempt to initialize and reinstall all the software on your macbook. Note that this will wipe everything off, so make sure you make appropriate backups before reinstalling from scratch.
Once you have reinstalled the OS, you can upgrade it to the most recent version and see if the problem persists before installing any other software that may interfere with it.
You really need to go through a process of elimination to find out whether the problem lies with the macbook or the router. However considering your iphone works fine, I would look towards the macbook first.

Self assigned IP Address, wireless doesn't work

After upgrading to Leopard I keep getting "AirPort has a self-assigned IP address and may not be able to connect to the Internet." when I try to connect to the wireless network. Thus, wifi does not work at all. I've researched it best I can and it seems to be a problem with the router assigning an IP address to the mac, but why didn't this happen in Tiger? However if I play around with it for awhile it will randomly start working, but the same method doesn't fix it everytime. It also works fine in bootcamp. If I physically plug into the router, it works fine. This problem didn't exist in Tiger at all.
Message was edited by: SuperDupe453

Follow-up:
On the two laptops, I finally managed to get on line by switching to a different wireless access point, on a different modem. I surmise that the communication between the Macbook DHCP client and the modem/router's DHCP server is less than 100% effective. Looking at the modem/router, I could see that all of the Macs had active connections. But, instead of showing the names of the Macs, the page showed a star (*) for each Mac. I had to compare Mac addresses to verify the connections. The MAC address, of course, is hard-wired into the computer's network interface. It appears that either the DHCP client didn't know what question to ask when it broadcast for an IP address, or it couldn't interpret the answer. Except in the case of the iMac, which worked perfectly.
I upgraded the MacPro last, since it is my primary machine. Same story--connection with self-assigned address, which is useless. However, this time, having nothing left to lose, I restarted the modem/router, which presumably dumped any inactive connections and issued new DHCP leases.
However, I do have a few words for the Apple GENIUSES! The Leopard network preferences page puts me in mind of a maintenance free battery. A few of the older folks will remember when you bought a car battery that had to be filled with distilled water to reconstitute the electrolyte. Then, periodically, you check the level of the liquid in the battery, and added distilled water when required. Adding water was required on occasion because some of the water would boil off under certain conditions. Then, we got the maintenance free battery, which is virtually identical to the older battery design, except that you don't have to perform the maintenance of replenishing the water. It turns out, however, that maintenance free batteries do vent on occasion, and should have water added. But, you can't add water because the battery is sealed. So, the difference between conventional and maintenance free is not that the maintenance free battery doesn't need maintenance, it is that you can't perform the maintenance without voiding the warranty.
The Leopard network preference page won't let you set the parameters that could restore a connection. If the DHCP client doesn't work automatically, you're stuck.

CAN'T CONNECT-self-assigned IP address

I haven't been able to connect to any networks for days. I keep getting this message in my network control panel under "status":
airport is connected to the network ABC. airport has a self-assigned IP address and may not be able to connect to the internet.
When I start getting this message, it happens to several different networks at once and on 2 different computers. What does this message even mean? That I'm out of reach or that I'm being intentionally blocked?

Ok, I have the fix!! After several frustrating days it finally just works.
The process:
Upgrade your Macs to 10.6 (Snow Leopard)
Powercycle your modem AND time capsule / airport TWICE
Reset your time capsule with a pin or paperclip on the back
Follow the prompts to setup your time capsule / airport access
-- On your Macs
Go to System Preferences > Network > Airport > Advanced > TCP/IP
Click "Renew DHCP Lease" then click "Ok"
Click Apply
Turn off Airport
Turn Airport on
IT WORKS!!!
One of the magical people at tech support walked me through it earlier today. The whole process took about 1.5 hrs because Show Leopard takes about an hour to install on one machine.
Hope this helps-
Joshua

Self-assigned ip address -- can't connect to Airport

I have a 2006 MacBook Pro which recently started exhibiting the exact same behaviour as reported by another poster in 2011:
For some reason the computer has started self-asigning its IP address and Network Preferences says that, because of the self-assigned IP, i cannot connect to the network.
I have two other Macs connecting to the same Air Port with no issues and I've tried to duplicate those settings on the MacBook Pro but still get the "self-assigned ip" message
Tried re-setting SMC and PRAM, no change.
The only change to my wireless setup was the change from a Verizon-owned modem to an owned Motorola unit (but the MacBook Pro connected successfully, many times, after the change).
I didn't knowingly change anything on the MacBook Pro -- from one day to the next it just stopped connecting.
I'm really at a loss to understand what's going on and, of course, not happy that the MacBook Pro can't connect to my network anymore! Help!

The wifi icon shows no connection with the network -- the "!" mark.
However the computer sees the network, i.e. when I search in Network Preferences the network is listed.
So: 1) the computer sees the network but 2) will not connect to the network. The reason given for refusal to connect is "self-assigned IP address".
Not to be repetitive but two other Mac laptops are connected to the same network and working perfectly. The network preferences, as shown in the "advanced" section, are the same for all machines, i.e. DHCP is selected and IPv6 is Automatic.

Self assigned ip address-Could someone help me?

There are two Powerbooks in my house which connects wirelessly to the internet and an airport express that joins the existing wireless connection.
When I'am using mine, I can connect without any problem, but when my girlfriend uses her mac we both get the self-assigned ip address. The only way to connect after that is by reseting the router.
This is what i did in both computers after I read some posts here (BUT THE PROBLEM CONTINUES) and I don't know what else to do:
"....1. Reset Open Firmware. As you turn on the machine, press & hold CmdOption+OF until you get a screen that says "Welcome to Open Firmware". At the prompt, enter "reset-nvram" (without the quotes). Press return. Enter "reset-all". Press return and the machine will restart.
2. Open network preferences. In airport, go to advanced. Check the box that says disconnect the wireless network when logging out. (It seems incredible that it would work, but apparently it sometimes does.)
3. Restart in "Safe" mode (hold down "Shift" while restarting). Once in Safe mode simply restart again in regular mode. http://docs.info.apple.com/article.html?artnum=306879
4. Go into your keychain and find the password key for your network. If you connect to a WAP it will be the name of that WAP. Then in the key click on the access control tab. It probably shows selected applications. Change this to "Allow all applications to access this item"........"
Thanks.
K.

My wife's PB G4 was doing the same thing. Worked fine at the Apple Store but had issues on my all Apple network at home. After resetting the routers, recreating the network etc I finally disabled the firewall and all seems to be working.

Self Assigned IP Address, wher the heck did that come from?????

Getting flipping well annoyed with this 10.4 software release! Come on Apple say something find the fix. The problem started with 10.4.4 EVERYTHING was working fine prior to installing, Wifes imac on airport, me on my G5 chatting happily away, the reason I purchased the .mac accounts and the iSights. After 10.4.4 came the problem of the iMac getting an IP address of 10.0.1.x from the airport and no longer able to connect to the internet. So I powered off the airport and connected the ethernet from the Zoom ADSL router direct, and the iMac claims there is a "self assigned IP address" on the Ethernet, which is not true, the machine uses DHCP, rebooted so many times (Windows funnily enough never needed as many reboots as OSX Tiger! and now seems like a better choice if truth be told) and everytime this self assigned IP address appears. Now if I connect my PB to the same cable I get 10.0.0.x and no problem with the internet connection. Settings are IDENTICAL, I even cloned my PB and booted the iMac from the clone and STILL we get "Self Assigned IP Address" on the iMac!
Does anyone have any idea how to stop the self assigned ip address problem?
Jed "Really not very happy at all" Stone

Powered off the Zoom DSL modem for an hour or so, and
now it all works fine, got this Gem of info from ther
Macosxhints website, a mighty fine site it is as
well. Regards Kev
Does not solve the problem for me. I'm sitting in a motel with a wireless net. I can connect to the Red Carpet network, with a strong signal, but Safari says I'm not connected to the internet. Network status gives me the same dumb "self-assigned" error. TCP/IP is set for DHCP. Since it's not my base station, I can't just go and recycle it. It did work once, but I haven't been able to reconnect. I've tweaked the connection multiple ways, rebooted multiple times, etc. etc. etc.
So what gives, and what can I do.
Powerbook G4, Mac OS X 10.4.6
Machine Name: PowerBook G4 12"
Machine Model: PowerBook6,8
CPU Type: PowerPC G4 (1.2)
Number Of CPUs: 1
CPU Speed: 1.5 GHz

Self-assigned IP address problem - My solution

I am new to this board and created an ID just to write this post. When I searched for this self-assigned IP problem, I found almost 1 million results on Google so obviously I am not alone.
I have this problem off and on on the wireless network at home with a Netgear router. It has never happened at my office with a D-Link router. Never happened at Starbucks or McDonalds (yes, they all offer WiFi here). But it happened at one Pizza Hut and it also at Christchurch airport about a week ago.
Deleting one of the plist files worked once at home many months ago but this week nothing worked. My Mac usually goes back to normal by itself after I "****" it out at other WiFi networks but not this time. As a last resort, I asked my brother (our family's I.T. guy) to change the router as I had not tried that fix. He didn't do it but a day later, he gave me to oddest solution that worked in a blink of an eye.
The solution? Key in a wrong password!!!
1) Go to Keychain Access, delete the keychain for the problematic network.
2) Connect back to the network
3) Enter a WRONG password that is similar to the right one. For example, if your password is Apple123, try APPLE123. You should still connect to the network and get a self-assigned IP.
4) Repeat Step 1. To be safe, you might want to re-boot now. I did but probably didn't have to!
5) Repeat Step 2
6) Enter the right password
I'm not all that techie so all I understood from what he said was:
1) It's probably a non-Apple router bug
2) It's a hex key problem. The password wasn't being encoded/decoded properly so the router wasn't assigning the computer an IP address. Wasn't even reading the password which is why I could connect with a wrong one.
He deduced that from reading a post from a guy in Spain who thought he had carelessly entered the wrong password and was wasting the community's time with his posting. I had read that post a couple of days ago too! But obviously I thought the Spaniard had just entered the wrong password and there was no fix for me to try out. My brother is a genius!
I guess it then makes sense why fixes like:
1) Disabling the firewall
2) Deleting preference lists
3) Deleting keychains
4) Changing the router
5) Renewing DHCP lease
6) Resetting the router
...have worked for many people and not others. None of them actually fix the cause of the problem. Having searched for 3 days, I could not find the REAL reason why this happened. Personally from all I have read, I think it must be a hex key problem with Netgear and Linksys routers. I see those 2 names mentioned a **** of a lot. Maybe it's another one of those gadgets built more for PCs that don't work perfectly with Macs all the time. We used to have an Apple Airport Extreme base station but that got fried by lightning. It was not cheap.... So technically, it really isn't Apple's problem. I think if we used an Apple router, we wouldn't have a self-assigned IP address. Maybe that's why they haven't "fixed" the problem after so many years.
Anyway, let me know if my brother's fix worked for you.
This is my good deed for the weekend! Goodnight....!

Hello, thanks for the tip/post, & a warm welcome to the forums!

Macbook Pro Self Assigning IP Addresses

Hi,
I bought a Macbook Pro in August of this year, that came with Lion. I had no trouble connecting to the internet in my apartment, and had no problem connecting to the internet on my college's campus. However, a few weeks ago, I brought my computer to campus and when I tried to connect to the internet, it said I could not connect because I had a self assigned IP address. By this time, my computer had upgraded to Lion 10.7.2. My college's campus does not require a password, so I just deleted it off the list in network preferences when I got back to my apartment and brought it back the next day. It finally seemed to work ok. Then I went to my friend's house over the weekend and she has a password for her internet, and after I entered it correctly, at first it told me the same error about a self assigned IP address, but then it finally connected. Today on campus, when I turned on my computer the first couple times, it worked fine. But now when I just turned it on again it came up with the self assigned IP address error again.
I'm not sure if there's anything I can do because this seems to keep happening inconsistently. But I was wondering if anyone had any tips, and I'm happy to provide any additional computer information because I'm not sure what else is necessary to know for this situation.

OK try this:
Open System Preferences/Network and for Location select Edit Locations
Click the + sign down left and create a New Location called 'Home'
Under Location then select 'Home'
Down left is a button with a cog and small down arrow on it, click that for a pop-up menu and select 'Set Service Order'
When that window opens drag Airport to the top of the list and put Ethernet second and Firewire third, click OK to close the window
Back in the main window click on Airport (at the top of the list) and then hit the 'Advanced' button down right
Click + and enter the name of your home wireless network and set the appropriate Security setting and enter the password - click 'Add' when done. Drag it to the top of the list if multiple items so it always tries that first.
Click the DNS Tab at the top then hit + and enter the Primary & Secondary DNS Servers supplied by your ISP, if you can't find these try using 4.2.2.2 and 4.2.2.1 - click 'OK' when done.
Click the TCP/IP Tab and set 'Configure IPv4' to Using DHCP and IPv6 to Automatic then click 'OK'
Click 'Apply' bottom right and you should be assigned an IP number by your router and have Intenet Access

ERROR: Wi-Fi has the self-assigned IP address

I'm having an issue with both my MacBook Pros at my home. If I try to connect to the Time Capsule after coming home from work, I receive the exclamation point in my wifi status icon and this error message in my network preferences pane:
"Wi-Fi has the self-assigned IP address 169.254.121.202 and will not be able to connect to the Internet."
The IP address is always different, but it always gives me a subnet mask of 255.255.0.0 and no Router IP.
This problem only seems to occur when both Macs are connecting and not connecting to the Time Capsule wifi. That is, when my girlfriend is out of town with her MBP gone, I never seem to have the issue.
It also seems like the first of our two to connect is the "winner" and will connect just fine, but the second one will not. If both computers are open and waiting to connect while we power cycle the Time Capsule, it will connect without any problem. If I then leave for work, come back home, try to connect, we have to start the same song and dance all over again.
I've tried just renewing the IP. I've tried restoring the factory settings on the Time Capsule.
I have a sneaking suspicion this may have something to do with the problem: My MBP is a 3rd generation copy of the data from hers. Hers was once my MBP, but we copied everything from it to a new MBP, which later was copied to a third MBP (the one I'm using now).
Thanks for any help anyone can provide!
Lou

I have a sneaking suspicion this may have something to do with the problem: My MBP is a 3rd generation copy of the data from hers. Hers was once my MBP, but we copied everything from it to a new MBP, which later was copied to a third MBP (the one I'm using now).
Thanks for any help anyone can provide!
Lou
That is interesting idea.. although the MAC address will be different I wonder if something in the GUID of the install being identical could cause issues..
Do both laptops have the same wireless cards?? Different models came with different cards. .these can not cooperate very well.. although I have seldom heard of them fighting in quite that way.
If you want to take the trouble.. a replacement hard drive and a new install of the OS.. see if it still happens.. how hard do you want to pursue it.
Check the log in the TC for when you try to connect.. and see if there is a reason given for not accepting you. Did you change the laptop network name.. ie they don't both have the same name do they.. it would not work if that was the case.

Self-assigned IP address after downloading Mavericks

Similar Messages

Maybe you are looking for