theshadow82

Q: My iMac's computer name keeps changing automatically after Yosemite upgrade

This started happening once I upgraded my iMac to Yosemite. It will add numbers to the name of my iMac.

 

Example: It starts off as say "My iMac"

 

Then a half day later, it changes to "My iMac (2)"

 

Then the next day it will be "My iMac (3)"

 

And if I open the Finder window, it will show "My iMac" and "My iMac (2)" under "Shared" but if you click on them, nothing happens.

 

When I go to System Preferences > Sharing the computer name will have the number there "My iMac (3)" and say it can be found as MyiMac-3.local

 

If I change it back to just "My iMac", the number process starts all over again. I even tried naming the iMac something it was never named before and the same process occurs with the adding of the numbers.

 

Anyone know how I can fix this?

iMac (21.5-inch, Late 2012), OS X Yosemite (10.10)

Posted on Oct 26, 2014 3:45 PM

Close

Q: My iMac's computer name keeps changing automatically after Yosemite upgrade

  • All replies
  • Helpful answers

first Previous Page 7 of 7
  • by farquaad,

    farquaad farquaad May 24, 2015 7:17 PM in response to farquaad
    Level 1 (9 points)
    May 24, 2015 7:17 PM in response to farquaad

    Oh bat crap II. It's back!

     

    Or rather, I contend it never went away, really.

     

    I was tired of my iMac going to sleep and losing network connectivity, and I believe since I ticked off the box Wake for network access, this nasty bug has returned, and my computer is now named Mac (2).

     

    So, stopped one problem (Mac now stays connected). Created another (Mac gets a name suffix). Brilliant.

     

    This was never an issue in Mavericks! This is progress?

  • by Colin Sutton,

    Colin Sutton Colin Sutton May 27, 2015 4:02 PM in response to farquaad
    Level 1 (30 points)
    Mac OS X
    May 27, 2015 4:02 PM in response to farquaad
  • by farquaad,

    farquaad farquaad May 27, 2015 4:28 PM in response to Colin Sutton
    Level 1 (9 points)
    May 27, 2015 4:28 PM in response to Colin Sutton

    Thank you Colin. Good to know. I will wait to see for sure! And then believe.

  • by Jeff Bailey,

    Jeff Bailey Jeff Bailey Jun 14, 2015 11:01 AM in response to Colin Sutton
    Level 2 (211 points)
    Apple Music
    Jun 14, 2015 11:01 AM in response to Colin Sutton

    I just installed the 10.10.4 beta and can report I have none of the problems described earlier in this thread.

  • by DigiTal00,

    DigiTal00 DigiTal00 Jul 5, 2015 3:00 PM in response to farquaad
    Level 1 (0 points)
    Jul 5, 2015 3:00 PM in response to farquaad

    A solution I used and seems to be working is switch to "used dynamic global host name" put the same name, added user and password and so far so good...

  • by Teresia Scott,

    Teresia Scott Teresia Scott Jul 17, 2015 8:51 AM in response to Colin Sutton
    Level 1 (30 points)
    iLife
    Jul 17, 2015 8:51 AM in response to Colin Sutton

    I have OS 10.10.4 and this hostname change just happened to me.  I have been running this version of OS for about 3 months and this is the first time this window message has popped up.

  • by Gary Stein,

    Gary Stein Gary Stein Jul 18, 2015 3:49 PM in response to Colin Sutton
    Level 1 (36 points)
    Jul 18, 2015 3:49 PM in response to Colin Sutton

    Sorry to report that this problem didn't happen to me until the 10.10.4 update, and it is happening to both my MacBook Air and my MacBook Pro which are the only Macs I have installed Yosemite on.

  • by meghanclare,

    meghanclare meghanclare Jul 20, 2015 9:20 AM in response to Gary Stein
    Level 1 (0 points)
    Jul 20, 2015 9:20 AM in response to Gary Stein

    This also is happening to me in 10.10.4.

     

    I somehow fixed it a couple years ago after much digging around and terminal messing (copying from other sites because I have very little knowledge there). I wish I'd written it down! I just got an SSD and did a clean install and now I'm seeing the dreaded "already in use" message.

     

    If using wifi and ethernet at the same time contributes to this issue: ridiculous. I use ethernet because it's fast and I use wifi to sync my devices, play to Apple TV and sync my password manager. I don't normally leave wifi on all the time but if I do it shouldn't cause a network issue. I would imagine many people use ethernet and wifi for these same reasons.

     

    It was cute and sweet though how people in this thread kept thinking new software updates would fix the problem. Apple doesn't fix software problems anymore. Apple just moves on to the next software release date. I'd also read big promises about fixing the dns issues with 10.10.4 but probably too much to ask that Apple might fix this six year old "already in use" bug.

  • by peterfromcable bay,

    peterfromcable bay peterfromcable bay Oct 11, 2015 2:04 AM in response to farquaad
    Level 1 (4 points)
    Oct 11, 2015 2:04 AM in response to farquaad

    Wonderful! I had thought I was dumb and was the only one with the problem because I was doing something wrongly. Your instructions were so clear and easy to follow, and sorted things out for me. Thank you.

     

    My problems appeared to start when I recently bought and used a Seagate 1TB wireless plus hard drive. I am really pleased with it because now it is like having an iPad with 1TB. It works both in wireless and usb modes. 

     

    But it seemed that every time the Seagate joined the network, my two iMacs and my emac had the problem incrementing their names by one. I did not ever originally have have any digits in their names. They were simply called "Older iMac" which is on OS 10.5.8, "Newimac" which is on OS 10.11 and an old emac. So the problem cannot be one introduced since installing Yosemite, since the emac and older iMac have had the problem. My wife and I each have an iPad - but these we do call iPad 1 and iPad 2. But oddly these names did not change, although the iMacs and emacs did! I had already two other external hard drives but they were not wireless but USB. They had never caused this problem. So in my simple mind it seems as though the wireless aspect of the Seagate in some ways is causing the problem.

     

    I am definitely not a computer buff but a wrinkled septuagenarian user. But the info I have given may help in solving a problem affecting many people.

     

    Peter

  • by Ohmyusername,

    Ohmyusername Ohmyusername Oct 26, 2015 3:44 PM in response to peterfromcable bay
    Level 1 (0 points)
    Oct 26, 2015 3:44 PM in response to peterfromcable bay

    +1 to

  • by Robster50,

    Robster50 Robster50 Apr 18, 2016 12:21 AM in response to Ohmyusername
    Level 1 (38 points)
    Mac OS X
    Apr 18, 2016 12:21 AM in response to Ohmyusername

    This problem seems to have come back in El Capitan 10.11.4!!!!!   :-(

  • by raitosan,

    raitosan raitosan Apr 27, 2016 10:46 AM in response to Robster50
    Level 1 (10 points)
    Apr 27, 2016 10:46 AM in response to Robster50

    I have this issue in 10.11.4.

first Previous Page 7 of 7