srpawski

Q: Late 2012 Mac Mini Ethernet Won't Connect

Everything was working fine up until a week ago.  I have not done any recent software updates to cause for issues.

 

I am running OS X 10.11.3.  I use wired ethernet.  My ethernet will not work.  Network Preferences indicates the cable is unplugged.  It is not.  I tried using a different cable and same results.  I have a managed switch and it still indicates that when the Mini is on that the port is powered up and has full 1000 duplex connection.  When I power it down the port turns off indicating there is nothing connected, when I turn it back on it powers back up.  Therefore, it does not appear as though the ethernet port has failed.

 

I have tried renewing the DCHP lease inside of the Network Preferences, disabling and re-enabling the ethernet service and still no luck.  Keeps coming back as ethernet is not connected.  I have opened terminal and ran ifconfig and get nothing.  I am unable to ping any external website.  I am also unable to log into my modem.

 

Wireless works fine.  I have a second, identical Mac Mini connected to the same hardware via ethernet which is working fine, so there doesn't appear to be any hardware related issues.  I am using all ubiquiti networks gear, 24 port POE switch and usg 4 pro router, all new 2 months old.  This has to be a Mac issue and has nothing to do with my equipment.  2014 Mac Book Pro works fine as well as 2 iPad Pros and 2 iPhones albeit wireless connections for them.

 

Any help is greatly appreciated.

Posted on Mar 5, 2016 8:04 AM

Close

Q: Late 2012 Mac Mini Ethernet Won't Connect

  • All replies
  • Helpful answers

  • by den.thed,Solvedanswer

    den.thed den.thed Mar 5, 2016 8:07 AM in response to srpawski
    Level 7 (27,639 points)
    Mar 5, 2016 8:07 AM in response to srpawski

    It has happened to others as well. 

     

    Take a look at > If the Ethernet connection on your Mac stopped working recently - Apple Support

  • by srpawski,

    srpawski srpawski Mar 5, 2016 8:50 AM in response to den.thed
    Level 1 (10 points)
    Mar 5, 2016 8:50 AM in response to den.thed

    Thanks for the reply.

     

    Ok, so I have confirmed on my non working Mini that I have the incompatible 3.28.1 kernel installed.  It installed on 02/27/2016 which is when I started having issues with connecting after I rebooted my Mini.

     

    I have followed the instructions, but the sudo software update -- background terminal command does not install the proper kernel to 3.28.2.  I ran through the steps 3 times, no dice.

     

    What kind of bull$**** is this?  There has to be another way to fix this without having to recover the OS.  Furthermore, am I guaranteed recovering it will fix it since what I did was supposed to fix it according to the article and it didn't fix it?  Why doesn't Apple just issue a software update to fix this?  I see many other entries in the log of the same incompatible kernel but with different versions over the last 3 years of having the Mini, but I have never had an issue with ethernet not working until now.

  • by den.thed,

    den.thed den.thed Mar 5, 2016 11:25 AM in response to srpawski
    Level 7 (27,639 points)
    Mar 5, 2016 11:25 AM in response to srpawski

    You should not have to do a wipe, reinstall and restore.

     

    You just need reinstall OS X from the App Store or run the OS X El Capitan 10.11.3 Combo Update over the top of the currently botched update.

  • by srpawski,

    srpawski srpawski Mar 5, 2016 12:53 PM in response to den.thed
    Level 1 (10 points)
    Mar 5, 2016 12:53 PM in response to den.thed

    Thank you.

     

    The support bulletin worked.  I ran through the steps again and rebooted twice and I am now back up and running on ethernet.  The systems information shows the correct updated kernel version installed.

     

    Apparently it needed some time to install and didn't install and update instantly as the bulletin made it sound like it would.  Since my other Mini and my Mac Book both had the kernel updates installed on Sunday with the bad one installing on Saturday, it must not have been able to update on its own since it wasn't able to connect online.

     

    Thanks again.