dbcm

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

After upgrading to 10.6.2 and upgrading EFI FW (don't know if it's related) i noticed that my ethernet stopped working. It detects the cable signal tries to negotiate IP through DHCP, the DHCP server gives the IP but the en0 doesn't use it.

I also tried manually configure the IP and also it doesn't work.

tried also with a old version of SL that i know everything was working but it doesn't work now.

tested with other routers and nothing

tested with SL DVD and nothing

any clues?

Macbook, Mac OS X (10.6.2)

Posted on Dec 17, 2009 6:19 AM

Close

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

  • All replies
  • Helpful answers

first Previous Page 8 of 10 last Next
  • by Johann Beda,

    Johann Beda Johann Beda Jun 27, 2013 6:25 AM in response to apple505
    Level 1 (4 points)
    Jun 27, 2013 6:25 AM in response to apple505

    If you are not using an ethernet connection (the ethernet port is not plugged in) then it is not possible for anyone to "hack" your system through ethernet.

  • by danfromoklahoma city,

    danfromoklahoma city danfromoklahoma city Jul 3, 2013 6:55 AM in response to dbcm
    Level 1 (0 points)
    Jul 3, 2013 6:55 AM in response to dbcm

    Resetting the router will usually do the trick.

  • by lenmak,

    lenmak lenmak Jul 21, 2013 2:14 AM in response to danfromoklahoma city
    Level 1 (0 points)
    Jul 21, 2013 2:14 AM in response to danfromoklahoma city

    Thanks Dan and others for responses.

    Over a year ago I wrote:

    >Summary: Airport to internet works fine, ethernet to my MacMini is self assigned on both machines and mini

    >can't connect. AFP connection works OK, can transfer files by drag and drop, so hardware is not the issue. >Tried most of the other "solutions" suggested in this thread- no dice. Is there NO-one at Apple networking >reading this stuff with understanding?

     

    As an ex-help desk person I am embarrassed to report it was PBKAC (i.e my fault combined with being confused by the error message) :-( . After a month or so of seething, I thought to check my security settings thoroughly. I had turned off internet sharing for the ethernet port. Turned on again and presto, all was well. :-)

  • by DrpabloC,

    DrpabloC DrpabloC Sep 25, 2013 5:25 AM in response to kickmyass
    Level 1 (0 points)
    Sep 25, 2013 5:25 AM in response to kickmyass

    Thanks so much kickmyass.

     

    I've never had this problem before in a decade, until it suddenly appeared and seemed unfathomable. My wifi was still working fine, and booting up from a mirror HD did not give the problem so I knew it wasn't a hardware issue.

     

    Spent many hours trying to fix this issue, trying all the other suggested fixes in this Discussion, but to no avail.

    But now just tried your cure and it's worked instantly. Suddenly my Router IP address via ethernet reappeared in the Network system settings, and all is well. Thanks a million. The link you posted details the cure, thanks for sharing it. (THANK YOU TOPHER KESSLER!). You have saved me a precious Saturday!

     

    P.S. I had this problem on dual 2GHz PowerMac G5 running OSX 10.5.8.

  • by Michael Viergutz1,

    Michael Viergutz1 Michael Viergutz1 Sep 27, 2013 8:18 AM in response to kickmyass
    Level 1 (39 points)
    Mac App Store
    Sep 27, 2013 8:18 AM in response to kickmyass

    THANK YOU !

     

    This problem was driving me crazy !

  • by ONCanada,

    ONCanada ONCanada Oct 1, 2013 8:39 AM in response to kickmyass
    Level 1 (0 points)
    Oct 1, 2013 8:39 AM in response to kickmyass

    Thanks a million. I am using a MacPro and just upgraded from osx 10.6.8 to 10.8.5. After the update finished and the system restarted, I could no longer connect to the internet. My system would get ip addresses in the 169.254 range on both Ethernet and wifi instead of getting a 192.168 address assigned by my router. Many solutions were tried and the one that worked for me was deleting the com.apple.alf.plist file. Thanks kickmyass.

  • by MHTSOSMAN,

    MHTSOSMAN MHTSOSMAN Nov 1, 2013 6:16 PM in response to dbcm
    Level 1 (0 points)
    Nov 1, 2013 6:16 PM in response to dbcm

    I think i find a solution. I open the router configuration and put an address reservation in every device to my network. I think it worked..

  • by renatafromsan francisco,

    renatafromsan francisco renatafromsan francisco Nov 9, 2013 3:44 PM in response to dbcm
    Level 1 (0 points)
    Nov 9, 2013 3:44 PM in response to dbcm

    Is it an "Ipv6" problem?

     

    I'm a total non technical person but...after wrestling with this for a few hours (wifi would connect fine, but ethernet got that error message), I adjusted the "Ipv6" option to "local-link only" in the Network settings, after clicking on the ethernet connection.  I've got a new iMac, running Mavericks, and was frustrated the ethernet connection wasn't working; using it through a Powerline adapter.

     

    So far, seems to have solved everything and ethernet is green/connected.

  • by brollyjohn,

    brollyjohn brollyjohn Nov 29, 2013 6:56 PM in response to princetoncheung
    Level 1 (0 points)
    Nov 29, 2013 6:56 PM in response to princetoncheung

    Same problem still persisting in Mavericks so upgrading is not a solution.

     

    This problem has been persisting since snow leopard.

  • by USD Business,

    USD Business USD Business Dec 9, 2013 8:41 PM in response to dbcm
    Level 1 (0 points)
    Dec 9, 2013 8:41 PM in response to dbcm

    I also had this problem, and after spending hours on the phone with out any help I figured it out. I just simply copied the IP address from the Wi-Fi, which is labeled under the turn Wi-Fi off button, then pasted the ip address to the ethernet by selecting using DHCP with manual address and putting the IP address in the blank.

    Hope this helps!

  • by fabienlefrapper,

    fabienlefrapper fabienlefrapper Dec 17, 2013 8:48 AM in response to renatafromsan francisco
    Level 1 (0 points)
    Dec 17, 2013 8:48 AM in response to renatafromsan francisco

    Thank you so much renatafromsan francisco!

    Here is the trick

     

    I adjusted the "Ipv6" option to "local-link only" in the Network settings, after clicking on the ethernet connection

     

    iMac 27 mid-2011

    Mavericks 10.9.1

    Airport enabled

  • by mikey86uk,

    mikey86uk mikey86uk Dec 27, 2013 4:28 PM in response to fabienlefrapper
    Level 1 (4 points)
    Dec 27, 2013 4:28 PM in response to fabienlefrapper

    Im now having the same problem for the last few days on my mid 2011 27" iMac, running the latest version of Mavericks.

     

    Ethernet works fine after i reset my router, but i think once it goes into sleep and then wakes it then for some reason decides to self assign a ip address.

     

    Changing the Ipv6 to local link shows something like a mac address as the ip address, is this right?

     

    I do have Apple care, so maybe worth phoning them in the morning.

  • by H. William Rhea III,

    H. William Rhea III H. William Rhea III Dec 29, 2013 7:06 PM in response to dbcm
    Level 1 (5 points)
    Dec 29, 2013 7:06 PM in response to dbcm

    My sons MacBook kept having this problem and it drove us nuts trying to figure it out.  We tried everything here and on other sites to no avail. 

     

    We have now fixed the problem for him, but I don't think the same fix will work for everyone.  For us, we had a bad port on the hub.  That's it!   He plugged his MacBook into other ports and it worked fine.  ****!  All those hours wasted and our problem was actually a hardware issue.

     

    BTW:  The hub is an older Asante model and the bad port kept pulling an 169.x.x.x number and was green, but never connected.

  • by RobertTheScot,

    RobertTheScot RobertTheScot Dec 31, 2013 1:04 AM in response to Johann Beda
    Level 1 (0 points)
    Dec 31, 2013 1:04 AM in response to Johann Beda

    Hi,

     

    There is an easy solution to this and I hope it works for you.

     

    1. Go to your network preferences.

     

    2. Select your ethernet connection.

     

    3. Go to location and select new location.

     

    4. Make sure the configure Ipv4 setting is set to: "Using DHCP with manual address.

     

    IMPORTANT

    5. Type in a new IP address. For example 192.168.1.70 (this will depend on how many IP addresses are allocated on your router network, to find out, download an app like "Fing" and it will tell you all the IP addresses that are allocated. Make sure to use one not being used by your system. Dont fill out any of the other boxes as this will be done by system.

     

    6. Save the changes you have made.

     

    That should solve it hopefully!

     

    See screen shot below for what you should be looking at.

     

    Screen Shot 2013-12-31 at 09.02.12.png
  • by StephanDavid,

    StephanDavid StephanDavid Feb 8, 2014 2:17 PM in response to kickmyass
    Level 1 (4 points)
    Audio
    Feb 8, 2014 2:17 PM in response to kickmyass

    This worked for me very well.
    Even when I was able to access Internet, I couldn't access other computers on network, or our network printer. Then came the Self-Assigned IP. Arggh!! So I trashed this plist file as well as the SystemConfiguration prefs folder.  For now, it's all working again. Thanks!

first Previous Page 8 of 10 last Next