Self Assigned IP Address Won't Go Away

My problem is described exactly in:
http://discussions.apple.com/thread.jspa?messageID=11784693&#11784693
However, none of the solutions there worked for me.
My old wireless router died, I bought a new one, and it allows me to connect wired but not wireless. Airport is on and I ran through the suggestions at the above link - no joy.
The problem appears to be that AirPort is self-assigning an IP address rather than getting one from the router. How do I get it to stop self-assigning and pull an address from the router?

WindSong wrote:
My problem is described exactly in:
http://discussions.apple.com/thread.jspa?messageID=11784693&#11784693
However, none of the solutions there worked for me.
You might try resetting your connection settings using the steps listed in this message:
http://discussions.apple.com/thread.jspa?messageID=10695921&start=1
They're not guaranteed to solve the problem, but they'll only take a minute or so to try.

Similar Messages

"Self-assigned IP address" won't connect to Internet

I have two Macs connected to my DSL modem: a MacBook Pro (10.5.2) and a PowerBook G3 'Pismo' (10.3.9). Yesterday both were working fine, but just now when I started up the PowerBook it told me "Built-in Ethernet has a self-assigned IP address and may not be able to connect to the Internet." Indeed, though the cable is connected just like yesterday, there's no Internet (though the MBP is connected just fine).
Anyone have any idea why this happens, and what to do about it? I've tried disconnecting/reconnecting the cable, and restarting the PowerBook, to no avail.

Your router uses a system called DHCP to allocate an IP number to any computer connected to it. So when a computer is booted, the router recognizes its presence and allocates it a number. If the computer is running 24/7 the number's 'lease' is usually renewed every few days.
Sometimes the process falls over and the computer fails to get an IP number from the router: when this happens it allocates itself an emergency number with the results you describe. As you found, rebooting the router usually clears the problem.
It may be possible to reprogram the router and the computer to use a fixed IP number, it depends on the router. Very possibly this would prevent the problem occurring since both ends would 'know' what the number should be from the off.

Ethernet has a self-assigned IP address and will not be able to connect

Other computers with same hardware and software (MacBook + 10.6) can get online using the same DHCP cable normally but mine can not. The self-assigned IP address refuses to go away no matter what I do. However, if I connect via wireless, everything is normal.
My 10.6 was upgraded a few weeks ago based on 10.5. Things were normal and Ethernet DHCP did work. This network problem suddenly appeared when the computer was functioning completely normal under a DHCP protocol using a cable.
Does anyone observe similar problems? Anyone has any clue about what's going on?
Thanks much!
--- Wei

try this. i had the same problem. found this on another forum:
1. Go to Mac/Library/Preferences/SystemConﬁguration
2. Delete the following:
a. Com.apple.airport.prefrences.plist
b. NetworkInterfaces.plist
c. Preferences.plist
3.Shut down computer
4.reset PRAM (hold commandoption+PR keys down before gray screen when booting up)

HT4628 My Mac Air OSX10.8.5 won't connect to the internet as it says it has a self assigned IP address and thus cannot connect to the internet. I can only connect to a network by manually typing in the configuration specs. Please help.

My mac air OSX10.8.5 won't connect to the internet. It says it has a 'self assigned IP address and therefore cannot connect to the internet'. Network diagnostics is unable to the solve the problem. It happened suddenly for no reason and now I cannot connect except by typing in the configuration settings manually. Please help me!

Use the Airport Utility or log into your wireless device via http and ensure the DHCP/NAT service is enabled. If accessing via HTTP, you will need to manually set an ip within your local subnet (eg: 192.168.0.x).

AirPort Express won't connect because of self-assigned IP address

For years, my old AirPort Express worked just fine. Then it quit (no little lights, no action), so I bought a new one.
Now I am running into the dreaded "apple self-assigned ip address 169.254.29.74" error, which is apparently a chronic Apple thing. There's discussion all over the internet about it, and nothing seems to help.
First, the equipment:
AirPort Express
OS X 10.6.8 (Please don't tell me to upgrade because my old hardware won't support the newer OS)
Processor 2 GHz Intel Core 2 Duo. (I don't have money for a new computer and this one is working fine except for this glitch)
Memory 1 GB 667 MHz DDR2 SDRAM
Actions taken so far:
Ran the AirPort setup utility (at least ten times)
Reset the AirPort to factory specs (at least ten times)
Deleted all the old Keychain references to the old network
Deleted all the old preference files, including one for a firewall
Reset the cable modem (five or six times)
Powered down the cable modem and turned it back on (only two or three times)
Physically typed in the IP address that works for Ethernet, but got the error message that it's being used by another device (This is insane because all the other devices that could connect are physically powered down. There's only one live computer trying to connect.)
Results:
I can get a new network to show up on the AirPort icon.
The Network part of System Preferences tells me that the problem is an apple self-assigned ip address 169.254.29.74 that won't connect. ("I made this and it's useless. Aren't you proud of me?)
Questions:
The documentation says this equipment will work with Snow Leopard. Is the documentation wrong? Should I try to find a simpler wireless router that doesn't demand as much from the computer?
Perhaps the AirPort is simply broken and I should return it for a new one?
Is there some secret work-around to defeat that self-assigned IP address glitch?

I am pretty sure the Express is running in the wrong mode..
The idea to plug the computer in is to check the setup.. not to need it permanently like that.. you can use either wireless or ethernet on the new express.. the old one you could only use wireless.
Please give me a screenshot of the setup of the express.
It must be in router mode.. ie when you open the airport utility and click edit.
Then go to the network tab.. it must show DHCP and NAT.. the DHCP range does not much matter..
But I also need to see that the wan port is getting an IP correctly.

Wi-Fi self-assigned IP address and won't connect to internet?

Hi guys,
Hoping someone can figure this one out for us as we're all starting to suffer from Wi-Fi withdrawal symptoms!!!!
We are using iMac OS X 10.7.5. We have an ethernet connection coming directly into the iMac from the vessel's server (working on a cable laying ship) and can still gain access to the internet on the desktop itself.
Up until this afternoon everything was working as per usual (iPhones sharing internet through network created on iMac, this needed reset roughly every 15-30 minutes in order for it to allow devices to access internet). But then all of a sudden nothing can connect to the Wi-Fi network. There are very short periods (5-10 seconds every 20-30 mins) where connections are made then drops out again. Have tried several different methods (renew DHCP Lease, create new location, etc) but nothing seems to work.
Then I noticed that our Wi-Fi had a Self-Assigned IP address (attached a screenshot below):
If anyone has any suggestions or ideas on how to remedy this problem it would be much appreciated, cheers .

Can your MacBook connect to any other Wi-Fi network or just not the one provided by your AirPort base station?
Was it able to connect before or has it never been able to connect to your network?

No Internet with Lion. Stay away until self-assigned IP addresses are fixed!

I have a TimeCapsule (802.11n 3rd gen) and four Macs. Until two months ago all was well and everyone could connect.
Two months ago the Apple apps on the MacBook Pro stopped connecting to the Internet on the TimeCapsule network (Mail and Safari would not connect, Firefox was fine). The MacBook Pro connects on all other networks. I travel a fair amount and the computer has connected fine at all networks tried. I have sinced updated to Lion (10.7.2) and the problem is the same. The error in System Preferences indicates that the computer has a self-assigned IP address and will not be able to access the Internet - but Firefox works, so we know that is not entirely the case.
Last week our desktop stopped being able to access the Internet using the TimeCapsule network. Problems the same as the MacBook but the desktop Mac is using Snow Leopard.
Our older laptop is using an earlier version of OSX and all is well. Out antique Mac laptop is also working well.
We also have a Verizon MiFi and all machines can access the Internet on that.
I have tried every "fix" I can find on the boards and through Google. Nothing works. From the looks of the boards, there are thousands of users with this problem and no answer from Apple.
I was much better off before I switched to Lion. In those days, I just used Firefox and looked at my iPad when I needed mail (and waited to sync at the office). But with Lion comes iCloud and an increased reliance on the App store, making internet connectivity through Apple apps is a must. Can someone from Apple help us fix this? Does anyone have any suggestions?

That is what I told Comcast, but they said since my
computer works "fine" in Safe-Boot,
Classic, and the other PC—then they
conclude there's no problem with their hardware and
that its not their problem; that its Apple's issue.
And nope I'm not connected wirelessly, it's through a
basic ethernet cable.
I don't know who to blame for this. Five years ago, this never happened, but it is common now. It affects both Macs and PCs, but as usual, people like Comcast will make an effort to fix a PC but throw up their hands with a Mac. Go figure.
So, what speed, duplex and adapter type numbers
should I put in?
I don't know for sure. Start with duplex. If it current says "auto", change it to "full". If that doesn't work, or if it already was "full", change it to "half". If still nothing, switch it back to "auto" and fiddle with all the 10/100 speed combinations. You may have to go back and try different duplex and speed combinations! It sounds harder than it is. Try changing the duplex and adapter settings from "auto" before changing the speed. I'm am on my work Dell right now (which needed the same fix BTW), so I can't give you very good step-by-step instructions.
The thing that troubles me is why is it that the
internet works fine in Safe-Boot and Classic, but not
Normal OS X mode?
No clue about that.

Self-assigned ip address starting with 169

Trying to connect to free wifi in paris but my gf's computer won't connect, instead it gives me a self-assigned IP address starting with 169, any thoughts on how I fix this?
Free wifi is a very big network in Paris, you only need a username and a password to sign in and can get connection almost everywhere in the city.
It works on my computer, but not on my gf's. It also works on my iphone, it's only her computer that doesn't connect. It worked on her computer aswell until yesterday evening.

Self-assigned IP Addresses 169.254.xxx.yyy are the ones your computer gives itself so that it has a name while it broadcasts a request for a better IP address. A self-assigned IP address usually persists for only a second until your Router responds with a good address. Finding yourself still stuck with a self-assigned address means you cannot reach the Router.
You should look for really fundamental problems. Is the connection method you prefer the top one in the System Preferences > Networks box? Are you too far away for a good connection? If all seems OK, use the ( Assist Me ) button in that panel and follow the Setup Assistent [not the Network diagnostics] branch to establish a good connection.

Self-assigned IP address, try to connect to pc

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 checked my sharing options, and everything looks to be on. I also have the yellow circle, but I can never get a connection unless it goes green. Before I upgraded, that was the issue before; it would be yellow until I changed the IPv6 connection to "link-local only" and then the ethernet connection would change to green, and I'd have no issues. Now, when I change it to "Link-local only" and hit apply, nothing happens, it's still yellow.
I tried to connect to the server just to see, and it won't connect. I get an error that says "There was a problem connecting to the server "AMANDA-PC" Check the server name or IP address, and then try again. If you continue to have problems, contact your system administrator."

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 get rid of self assigned IP address

Hello,
I have been trying to resolve this problem by myself for the last 4 days (by googling and reading forums) but nothing works so here I am.
I moved last Tuesday and everything worked fine until that day. Since I am in my new apartment, I can't connect to the Internet because of a self assigned IP address. Here is more info:
-I have a new modem since I moved (the apartment where I was living was furnished and had a modem already). However, I am using the same service provider and modem than the apartment I was subletting.
-I only have a modem (no router) and I use the Ethernet to connect.
-I am writing this message from a PC laptop which confirms that the modem is working fine and that the ethernet cable is fine, etc.
-I did many rounds of shutting down the computer, renew DHCP, unplugging the modem (from 1 minute to 10 hours) and plugging everything back.
-I called the ISP but they could not help (they just repeated the same instructions that I could find in the guide)...They have no idea how I can get rid of the self assigned IP address.
The problem is still the same, I can't get rid of the self assigned IP address (169.xxx).
Please help if you know other tricks to fix that issue...
Thanks a LOT in advance!!
Julie

Re 1) Setting up a new account won't solve the problem in itself but it will help narrow down the cause. The idea is this: the problem might be caused by something system-wide (e.g. a preference file in /Library/Preferences) or it might be caused by something that is specific to your account (e.g. a preference file in yourhome/Library/Preferences). If we knew which, we could target the troubleshooting appropriately. The easiest way to figure out which is to create a new user, log in as that user and see if the problem remains. If it does, it must be system-wide; if not, it is specific to your account.
Are you using any firewall software? If you are using Tiger's built-in firewall, how is it configured?
- cfr

Ethernet cord has a self assigned IP address, can this be changed?

I am trying to connect my laptop to my Xbox 360 so I can get on Xbox Live using my computers wireless as a gateway... but the ethernet cord has a self assigned IP address and won't work.. I've tried everything to change it and it still won't connect with my router. It is a cisco router.

Welcome to Apple Support Communities
You stand a better chance of a connection if you set the Ethernet interface to DHCP and have it be assigned an IP number by the Router ...

All of a sudden I started getting "Self-assigned IP address ... Can't connect to internet" message when I attempt to connect to wi-fi at home. I tried solutions posted on the net but to no avail.

It once worked when I removed it from Network preferences and attempted a relogin - but the problem resurfaced again and is not going away. I tried the "key chain access" solution - but my Wi-Fi doesn't show up in "Sytems" at all. Any help will be appreciated. It's OS 10.6.9 MacBook Air.

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 problem?

There are times when my Mac Pro (Lion) won't connect to my home internet and comes up with a message about a self assigned IP address. I have no idea how to solve this. At the moment I just have to keep trying to connect and sometimes hours later or the next day it will. Its very frustrating! Does anyone know what I can do / what the issue is please.

Hold down the option key and select the Wi-Fi menu in the menu bar. What values are shown for the following?
PHY Mode
Channel
Security
Signal/Noise or RSSI
Transmit Rate
Please do not post the BSSID, as that information is private.
Now hold down the option key again and select
 ▹ System Information... ▹ Network ▹ Wi-Fi
Compare the two-letter Country Code with the ISO code for your country. Does it match? The code X0 means that the country couldn't be determined. The code X3 means South America, not otherwise specified.

Self-assigned IP address problems

I'm having a problem with my wireless router connection (my Airport card shows the network, but the "fan" is greyed out, and if I choose the network it still doesn't connect - When I check network status I get "AirPort connected to network, but has self-assigned IP address and may not be able to connect...)
I can temporarily fix the problem by going into System Preferences to Network to Airport to Preferred Networks to Assist Me and THEN it will go to my network and turn on the path.
I'm running Tiger 10.4.11 on a G5 iMac with the original AirPort Extreme card, and routing through a Linksys WRT54G attached to a cable modem.
There are a lot of networks in my area, according to my wireless "fan".
If changing channels on my router might fix this, I'd like to give it a try, but I don't know how, AND I don't want to ruin the signal to the other computers in the house, which, by the way, work just fine when the iMac loses the signal.
If there's another way to tell the router to ignore the self-assigned IP address, or to get the AirPort to stop providing this ...
The problem is obviously the self-assigned IP address. The question is what is causing this?
Is it the AirPort Extreme Card?
Is it the Linksys Wireless router?
How do I test to see which it is, without losing the signal from the router to the other computers in the house?
With so many people having the same problem, there must be an answer somewhere.
Can some kind soul please point out the correct path? My tech support (teenager) will be home from college this week, and if I can prove to him that it won't ruin everything I think he'll be up to the challenge.

Hi,
Thank you Linc & dwb, I've had no issues with the router in the 14 months its been installed. But tonight I've turned off the NAS and since then no drop off for wifi/ or assigning itself an IP address.
I will switch on the NAS once again and see what happens, would it be best to assign a static IP to the NAS? One thing I have found when checking the homehub connection details, the mac air connects at the 5Gz Wireless as does the Kindle, which has also suffered from losing the wifi connection, where as my macbook pro only connects at 2.4Gz and like I said has not had any issue. Not sure if this anything to do with the problem or not?
All I do know is that since the NAS was introduced then the problems began, so again not sure if its the NAS impacting on the router or a router setting?
thanks

Self Assigned IP Address Won't Go Away

Similar Messages

Maybe you are looking for