OS X keeps appending "(2)" to computer name

[theSeb]

Yep, thats what I said:

"I have never gotten better speed, reliability or distance with 5GHZ anyway..."

This isn't about that. It's about Mac's being renamed with (#'s)

I don't think you've actually read what I said. Your solution to the problem is to switch off 5 GHz and then you justify this, because you have never gotten better speed with 5 GHz and you added a flawed test as "proof" that 5 GHz is not faster.

It's easy, if you use a very simple analogy. Picture the wifi channels like roads. Just because you have a shiny and fairly straight multi lane freeway, you can't drive any faster on it, unless your car is capable of driving faster. Your Trabant that tops out at 90 MPH on the normal road, isn't going to magically go faster on the freeway. That does not mean that other traffic can't go faster on the freeway.

 

[dannys1]

The people popping up in this thread saying "its not to do with Yosemite" are damn annoying.

There's 25+ people in this thread, including me, all with this specific issue with Yosemite, just because you've had it for other reasons prior to Yosemite doesn't' mean its releated.

This IS specific to some systems on Yosemite (my rMBP for instance, not my iMac or Mac mini) this IS a Yosemite bug, we've established that. So please, shut up.

Unfortunately i've tried every fix in this thread and many more and none have worked, work up today to find " rMBP (2)" in my shared devices list.

Yosemite has more bugs that i've personally experienced than any other OSX version previous.

 

[Intell]

Why should those that say this problem isn't unique to 10.10 stop saying that when they have the same problem on older versions of Mac OS X. For all we know it is caused by the same bug or feature. While dislike it all you want, this event has been happening since 10.6.

 

[GlenK]

I'm at 9! WOO!!!

Ditto, I'm at 9 too!!

 

[F1Mac]

I haven't counted them this morning but it's like I'm running a whole render farm as well

That's something that will be fixed soon hopefully.

 

[dannys1]

Why should those that say this problem isn't unique to 10.10 stop saying that when they have the same problem on older versions of Mac OS X. For all we know it is caused by the same bug or feature. While dislike it all you want, this event has been happening since 10.6.

Because it hasn't been this exact bug, you've had something similar and different and your initial fix has nothing to do with it and now you're just blurring the lines of a legit bug that 25+ people in thread have got in Yosemite and never before.

 

[Intell]

But we don't know that. 10.10 could have changed something else completely unrelated to this problem that makes the incrementing computer name occur more than it has before. The initial fix does correct the problem for many people within this thread. That alone shows that the bugs are very similar in nature.

 

[ElectronGuru]

Probably a coincidence but my issues with this went away when I set up IP address reservations:

http://www.macinstruct.com/node/553

 

[dannys1]

Probably a coincidence but my issues with this went away when I set up IP address reservations:

http://www.macinstruct.com/node/553

You'd think this would work wouldn't you considering it seems to have a ghost in the network but i've had my setup and still get it.

 

[fisherking]

This is caused by your computer seeing a ghost of itself on your network. You can make it stop by turning off Wake for Network Access in the Energy Saver pref pane. Once off, rename your machine to finish.

this has now held for me for a week (well, 6 days). btw, thanks intell...

 

[adnbek]

I'm getting this issue now too and it's definitely Yosemite related. I'm aware it used to occur in previous OSes in limited circumstances, but i never had that issue personally with my setup. With Yosemite though it occurs constantly now, causing issues with any remote access software (steaming, vnc, etc.). Since Apple is aware of the issue, I'm hoping it gets fixed soon.

 

[iapplelove]

Didn't see this topic covered as I posted a thread about this a few days ago. I also get a (2) next to my MBP. Wasn't happening before Yosemite install.

 

[meme1255]

It's really annoying ...

 

[Trebuin]

I have the same problem...up to 8 copies with wifi wake enabled...need it enabled.

 

[snarfquest]

This is caused by your computer seeing a ghost of itself on your network. You can make it stop by turning off Wake for Network Access in the Energy Saver pref pane. Once off, rename your machine to finish.

This worked for me.

 

[GlenK]

This worked for me.

It worked for me too, but what does that actually mean, "wake for network access"?

 

[theSeb]

Issue hasn't come back for me now for a couple of days. Happiness!

I tried all of the fixes mentioned in this thread and none of them helped. I simply just kept renaming the Mac in the sharing preferences and threatened it with my fist. I think it finally got the message and decided to stop doing it.

 

[Macsterguy]

Where are you going with this?

I don't think you've actually read what I said. Your solution to the problem is to switch off 5 GHz and then you justify this, because you have never gotten better speed with 5 GHz and you added a flawed test as "proof" that 5 GHz is not faster.

It's easy, if you use a very simple analogy. Picture the wifi channels like roads. Just because you have a shiny and fairly straight multi lane freeway, you can't drive any faster on it, unless your car is capable of driving faster. Your Trabant that tops out at 90 MPH on the normal road, isn't going to magically go faster on the freeway. That does not mean that other traffic can't go faster on the freeway.

Your completely off topic....

When apple fixes this at the next update (we hope) I, we, you can turn 5GHZ back on... You preaching to the choir here… I maintain 30 macs and many more PCs.

Not really looking for a class on Internet highways/Freeways whatever you're ranting about.

The best thing we can do is give feedback to Apple not each other.

 

[Trebuin]

Wake for network access is for servers or remote users primarily. Basically, it allows someone to send a "wake on LAN" (WOL) or "Wake on wifi" to wake the machine. Wake on wifi currently has a lot of issues/is very hard to customize. I use this because I want to send a WOL packet to wake my computer...I put it to sleep to save on my horrific electric bill.

Most people should't need that option. I'm still working with it, but am currently using a timed wakeup/sleep program and just know I can only start a remote into my computer between certain times.

What we're seeing is probably the computer trying to register the bonjor proxy and that is not functioning correctly. Hence why the WOL doesn't work correctly either. Now it just shows the old session as still there and the router sends an ip conflict. I saw one the first time I saw this issue.

 

[GlenK]

Wake for network access is for servers or remote users primarily. Basically, it allows someone to send a "wake on LAN" (WOL) or "Wake on wifi" to wake the machine. Wake on wifi currently has a lot of issues/is very hard to customize. I use this because I want to send a WOL packet to wake my computer...I put it to sleep to save on my horrific electric bill.

Most people should't need that option. I'm still working with it, but am currently using a timed wakeup/sleep program and just know I can only start a remote into my computer between certain times.

What we're seeing is probably the computer trying to register the bonjor proxy and that is not functioning correctly. Hence why the WOL doesn't work correctly either. Now it just shows the old session as still there and the router sends an ip conflict. I saw one the first time I saw this issue.

Thanks for the explanation. I kept thinking I might be turning something off I need. It did work so far though..

 

[iLog.Genius]

That doesn't work for me. I still keep getting a number beside my name. At first it was amusing, but now it's just getting pretty annoying.

 

[Trebuin]

Update:
Called up apple about this while dealing with another problem and they pushed me to a section that is working on an update fix to this very issue.

----------

That doesn't work for me. I still keep getting a number beside my name. At first it was amusing, but now it's just getting pretty annoying.

The root of the problem may lie in the WOL being enabled and/or, go into sys preference/Sharing, and see what is enabled. I have File Sharing, Remote management, and Remote apple events enabled. Disabling all of those may fix your problem.

 

[randomgeeza]

I seem to have resolved this for now. I simply turned off my TC, and whilst that was rebooting, I renamed my Computer in System Preferences, restarted the MBP and it seems to have worked (for now). BTW was up to (3). And I have never seen this issue before on any of my units, on previous versions of OS X. ?

 

[theSeb]

Your completely off topic....

When apple fixes this at the next update (we hope) I, we, you can turn 5GHZ back on... You preaching to the choir here… I maintain 30 macs and many more PCs.

Not really looking for a class on Internet highways/Freeways whatever you're ranting about.

The best thing we can do is give feedback to Apple not each other.

Yeah, because the 5GHz channel is the issue. Your "solution" is not a solution. You maintain 30 Macs and are quoting speedtest.net results to prove that the 5 GHz channel isn't any faster than the 2.4 Ghz channel?

 

[Icaras]

I had this issue for a good couple of years actually, but I kid not, for some reason I haven't had the issue for about a week now. But the week before it was actually persistent and I kept getting iMac (3) every single time it woke up from sleep.

Now it seems gone. Not sure why, but it is. Though i don't know how long this will last. I'm running Yosemite, but the problem was still there when I first upgraded.