It isn't a 10.10 bug, this problem has been around since Apple introduced Wake On Wireless in 10.6.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
OS X keeps appending "(2)" to computer name
- Thread starter BriMercer
- Start date
- Sort by reaction score
It isn't a 10.10 bug, this problem has been around since Apple introduced Wake On Wireless in 10.6.
It may have been around in a limited way since then, but 10.10 definitely broke it. My iMac has been fine for months, but I installed Yosemite when it was released, and it immediately started going up in numbers.
I have tried this and it's not working here unfortunately. rMBP(2) disappears when I do this but after about 10 seconds it reappears and then every minute, or so, it disappears, and then reappears again.
Did you try changing your Location Name in Network preferences to match our computer name?
Can confirm it's happening to me to and even though the computer functions fine, handoff works great, it's driving me nuts. I tried restoring and resetting my AirPort Express, nope. I've tried
Code:
sudo scutil --set LocalHostName "MacBookPro"
Code:
sudo killall cfprefsdI clean installed 10.10 on a rMBP that had been running 10.9. When I open safari on my iPhone, under iCloud tabs I see 'MacBookPro' which had tabs from my 10.9 install and tabs from 'MacBookPro (2)' from my 10.10 install. Apparently it takes two weeks of inactivity to clear the old tabs form the 10.9 install out of iCloud, so could this be creating an issue? Perhaps after two weeks the name change back to 'MacBookPro' will stick??
Nope, this has become more problematic or broken in 10.10. I saw several dozens of customers reporting the same issue with Yosemite, damn near zero before 10.10.
I saw the same problem on my Yosemite Mac with zero problems on all of my other Macs running Mavericks.
Count me as one that didn't have this problem before 10.10
seems to be impacting other file sharing apps for me as well. I tried the wake up change and that didn't help (knowing me, I may have done that wrong anyway.) MacBook seems to be working fine, just seems to be cloning itself everywhere.
I was about to post a thread about this myself, but I'm glad others are seeing the same thing. The ghosting explaibation makes a lot of sense, I just don't know what will be the definitive fix. I'll try all the other suggestions tomorrow and see what happens. I've actually fixed it temporarly more than once but it always comes back in a matter of minutes.
I've had this issue for a year or so. I change the name back to MacBook Pro every couple of months than back it goes to MacBook Pro 2 or 3 or 5. Just turned off wake for network to see how that works.
The issue is still here and I've tried all sort of things. The annoying part is that it's causing small issues with the Time Machine backups to the time capsule, because the file used to be called rMBP.sparsebundle and then TM was not happy because it now needed to create rMBP (2).sparsebundle. Not the end of the world, but it breaks the automatic backups occasionally with a warning that somebody is trying to hijack my backups! lol.
turning off 'wake for network access' in energy saver still working here.
no added # to my mac's name in 2 days; a record for me since running the 10.10 beta....
no added # to my mac's name in 2 days; a record for me since running the 10.10 beta....
No issues with Mac Pro, even though wake for network access is enabled. It's only happening on the rMBP.
I changed the network location to match the computer name, turned off the wake on network activity.
The problem persists... Checked my Time Machine backup and found it is affecting that as well as mentioned a few posts back by another user. This thing is starting to on my nerves...
That other user was also me
. Yeah, I have done everything that you have mentioned and was suggested in this thread and it wasn't working properly until this evening, but.... I have the location back to automatic, and wake for wifi network access on and for a giggle I decided to change the network for one last time by removing the (2) from computer name in sharing, and, for some unknown reason, it is still working a couple of hours later! Don't ask me why because changing it over and over again for the last two days didn't help.