Ethernet problem - self-assigned IP address

I'm just testing my spanking new Mac Pro with Leo 10.5.6 (still holding back to go to 10.5.7 as there are issues with certain audio apps) and I can't get an internet connection via ethernet and a router. In the network config I get the dreaded 169.xxx.xxx.xxx address and the message "Ethernet 1 has a self-assigned IP address and may not be able to connect". (ethernet 2 has the same problem). Manual DHCP does not work either.
The router is a D-Link DI-624 connected to a cable modem.
I have absolutely no problem connecting to the internet with my Macbook or any other PC through the router.
Strangely, the Mac Pro can connect to the internet and gets an IP if directly plugged into the cable box. However as I often need a wireless connection I need to keep using the router.
Apart from an answer, I would also appreciate if we could avoid wasting time by asking the typical first level help desk questions, such as "have you restarted the router?" etc. I'm not computer illiterate and all the symptoms and logical deductions clearly indicate that the problem is solely in the Mac Pro.
Thanks much.

I'm having the same problem.
I have a brand new router and switch, everything works fine when I plug the cable into my PC Laptop and worked fine with my Mac Pro until today!
Now, I get the nasty "169..." self-assigned IP on both Ethernet ports and cannot connect to the internet.
I have deleted both the ETHERNET 1 and ETHERNET 2 Prefs as R2B suggested but sadly, it did not work for me. As I reassign the Ethernet, it gives me the same error
any ideas??
thanks!

Similar Messages

Ethernet has self assigned IP Address,will not connect to internet?

Ethernet has a self assigned IP Address and will not connect to the internet.
I am on - Mac os X - 10.7.5
Using a BT Broadband Router, my power mac is connected to the network via TP-Link Plug POWERLINE. This has worked great for ever!
A week ago, my web connection dropped, network settings say "Ethernet 1 is active and has a self assigned IP Address and will not connect to the internet"
This seems to be a popular thread and I have followed all the answers I can find and the problem remains.
I also run a Powerbook on the wireless internet and other appliances such as, iPads, iPhones, and the wireless is fine.
My sky box and Xbox 360 (both ethernet via TP-Link) also have NO connection.
When I turn my laptops wireless off and try the ethernet cable (tried a new one too) instead, there is the same SELF-ASSIGNED IP ADDRESS issue.
This point me to the router or TP-Link network. I have replaced the router, same errors.
On my Powermac I have -
Deleted 'system configuration from the system folder - as advised by apple.
Tried swapping from DCHP, DCHP Manual and renewing lease etc.
Could anyone help at all? I am lost now as how to solve the problems.
All my TP-Link power line extenders show the correct lights, i.e., all on and yellow.
I am not experienced in networks, this is driving me mad now!
Any help would be appreciated
Thanks
A

Open System Preferences/Network
Select the Location you use at home
You may need to click the Padlock bottom left at this point if it's locked, enter the admin password to unlock
In the left hand column drag the Ethernet connection to the top of the list and remove any you don't use
Click the Advanced button bottom right
Click the TCP/IP Tab
Set Configure IPv4 to Using DHCP
Click OK bottom right and you should see the Router IP number appear and a unique but similar one for your Mac
Click Ok then click Apply and close the Panel

Ethernet Self-assigned IP address

I am running Tiger and recently ran into connectivity issues. I am getting the message that I have a self-assigned IP address and cannot connect to the internet. I have had no issues for 3 years and all-of-a-sudden I get this message. A pc laptop was able to connect with same modem and ethernet cable with no problem. I have seen discussion topics like this on here, but the majority of them are running Leopard. Please help!!
I have been through NUMEROUS trouble-shooting phone calls with my service provider and had 3 techs out to my house and no one can figure out the problem.
Here is what I have eliminated:
1. Rebooting the modem
2. New modem (actually three new modems were tried)
3. New ethernet cables
4. A trip to the Apple store to verify my NIC card wasn't bad...it connected instantly.
5. I brought my machine to a neighbors house (who uses the same provider) and it also connected instantly
5. Quadruple checked my network settings.
Any tips or advice is appreciated!

Your computer can connect at the neighbor's house and at the Apple store with no problems, but at your house you can't connect at all? Therefore your computer is fine but your home ISP is bad. But a different PC can connect at your house, so therefore your home ISP is good. There's some missing information here, this just doesn't make sense at all. Maybe a weak signal from the ISP that is bad sometimes, but not all the time?
If the Apple store and your ISP can't help you figure this one out where they can actually check out your machine and hardware settings, then I think getting any help here with a limited flow of information will indeed be very difficult. I had a hard time understanding exactly what your problem is and what you can safely rule out as the culprit.
Cancel your ISP service and sign up with another provider if they can't get it working for you, that's what you are paying them for. The Apple store said your machine is working fine, right?

AppleTalk & self-assigned IP address using ethernet

How do I find or assign the IP address for my Ethernet 2 port?
I have two ethernet ports on my Mac Pro. The first one I'm using for the internet and is working fine. On the second one I've set up a local AppleTalk network to connect to my serial postscript laser printer through an iprint adapter.
The status is connected and I was able to print. But System Preferences has the message: "Ethernet 2 has a self-assigned IP address and may not be able to connect."
From reading these discussions a "self-assigned IP address" is a problem. Or is it okay? I'm using "Using DHCP" to configure because that option got me connected. Or should I manually configure? How do I find (or assign) the IP address? Obviously I don't understand much about networking.
Thanks!

Self-assigned addresses are not a problem in situations like you describe.
In fact that's what they're designed for - for interconnecting systems that just need to talk between themselves and not to other hosts on your local network or the Internet.

Ethernet has a self-assigned IP address and will not be able to connect to the Internet. on host mac

im using a cross over cable from a macbook pro{mavrics}, to a imac {lion}. ive been sharing internet from a dongle no problem for months but now it started saying Ethernet has a self-assigned IP address and will not be able to connect to the Internet. on the macbook. and every thing is hay ok on the imac ¿¿¿ ive been googling all day to no avail

System prefs > Sharing. seroapple wrote:
im using a cross over cable from a macbook pro{mavrics}, to a imac {lion}.
Don't need a crossover cable.
Make sure System prefs > Sharing is set up correctly.
-> https://support.apple.com/kb/PH13855?locale=en_US

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

Ethernet has a self-assigned IP address and will not be able to connect to the internet
The problem appears to have been a connection error as well as the system preferences which have reset with a 'valid' IP address after a system preferences 'reboot'.

Power off your internet router. Disconnect completely from its mains power by pulling the plug out of the mains socket. Disconnect all ethernet leads and cables to the router. Wait a minute or so and then reconnect all cables and turn on the power. See if your internet starts.

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)

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 !

Can't connect to internet..self assigned ip address problem with DSL Modem

I've run into this before, without resolution, and now again on a friend's iMac. Time to ask around...
Basically, everything appears to be assigned and configured perfectly, but the network status always shows, "...you have a self assigned IP address and may not be able to connect to the internet". Sure can't connect to the net when it says that.
I've gone thru the procedure advise before that details the sequence of events needed to insure the modem resets and recognizes the Mac and it's incoming DSL (sbcglobal) signal. The order of network priority is set properly by dragging built in ethernet to the top of the list. Modem was powered down, plugged in, and then connected to the Mac, but no solution. Any ideas? thanks

This continues to be a mystery. I've had my powerbook on several networks, and connection has, most of the time, been an automatic process. Additionally, I've installed new systems for people with the same isp, and all has been well. So easy is the process, it's never been an issue. However, following explicit procedural instructions (including powering the Mac down), has proven unsuccessful on 2 different occasions.
There is little help with the isp support in India, which is where the call routes too.
The only thing I have not done is to swap out the cable at one of the locations, but the other location, which has the same issue, works fine on the iMac there. Only when I connect my Powerbook to the modem, does the "...self assigned ip address...not be able to connect to the internet" appear.
I just keep thinking there has got to be a small detail that is being overlooked.

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 ...

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 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!

Why does my Airport Express say "self assigned IP address"? No IP address for the ethernet, and it is not connecting to my cable router any longer...

Why does my Airport Express say "self assigned IP address"? No IP address for the ethernet, and it is not connecting to my cable router any longer...

Some cable providers.....like mine, a well known company......seem to take anywhere from a few moments to sometimes up to 30 minutes to allow their equipment back at the cable company to fully reset and issue a new fresh connection.
So, it would not hurt to leave things powered down for 15-20 minutes or more when you perform the reset that John Galt suggests.

Problems connecting Airport - self assigned IP addresses

Greetings,
I upgraded to a powerbook a few months back, and everything seemed to be working well enough until today. My internet connection (using airport on my powerbook) wasn't working. Usually I just unplug my modem, reconnect, and all works fine.
Today, to my horror, airport does not reconnect as usual and I see the note
AirPort has the self-assigned IP address xxx.xxx.xx.x and will not be able to connect to the Internet.
I've tried using snow leopard cache cleaner, I've tried restarting, I've turned off my iPhone, and disconnected my old mac connected by ethernet.
My iPhone works, using the same wifi, and there are other wifi users nearby.
Not sure what else to mention, any ideas?

try to do it manual:
decide a ipv4 close to your iphone (if iphone has xxx.xxx.x.7) like x.8
next, net-mask must be 255.255.255.0 (if there is something other it's wrong)
router is seen when you open network in iphone, take this.
could be like: 192.168.1.1, if your ip starts with 192 ...
all this in network/more options

Airport - Self Assigned IP Address Problems

I moved into a new place recently and having problems with my Airport connection on my MacBook Pro. I get the error
"Airport the self-assigned IP Address 169.254.23.207 and will not be able to connect to the internet" (obviously the IP varies)
It's only happened ever since I moved into this new place. Comcast is our ISP and we're using a Netgear Router my step brother bought a while back. I logged into the Router and all settings seem to be normal as far as I can tell. It only happens if the computer goes to sleep or is shut off, any situation where Airport is disabled. I usually have to keep turning Airport On and Off until it comes back. I logged into the router, none of the settings seem wrong. The ISP setting is set to Dynamic IP. It's using WPA and doesn't seem to have a problem with the key.
Here's a screenie: http://img217.imageshack.us/img217/9797/screenshot20100924at502.jpg
What could be causing this problem. It's extremely frustrating.

Of course a search for "macbook and connection dropouts" results in numerous pleas for help. That is what you searched for. Did you expect your search to find the millions of users who are not having "macbook and dropout" issues?
FWIW there are many reasons why a wifi connection will "fail or dropout", one of which may be a hardware issue. But more likely is interference, configuration, firmware, router, setup, security, not reading the manual, etc.
What would lead you to believe "Apple technicians apparently are mystified."?
I doubt very much that Apple is involved in a conspiracy of silence "Given all the macs with this problem, why is Apple silent on a fix? Is this actually a hardware problem that would require the replacement of every motherboard in every mac notebook with a faulty broadcom wifi chipset? " But then I don't subscribe to many conspiracy theories.
There are many more Macs without the problem you and others here in this help forum describe than there are with the problem.
Message was edited by: BobTheFisherman

Ethernet problem - self-assigned IP address

Similar Messages

Maybe you are looking for