I spoke with a senior tech at Apple about this just now. I discovered that the changing computer name has made my TimeMachine backups unaccessible - the permissions are all FUBAR. So in addition to being extremely annoying to see the computer name constantly changing, I cannot get to any TM backups. The Time Capsule sparsebundles cannot be loaded - when I attempt to mount the drives and view the sparsebundles, I get an error saying they are temporarily unavailable. Within the TimeMachine, all of the folder icons have little red dots on them.
He suspected corrupted network files, and suggested the following to fix the issue of the computer name changing:
Go to Macintosh HD > Library > Preferences > SystemConfiguration
and delete the following files:
com.apple.airport.preferences.plist
NetworkInterfaces.plist
preferences.plist
Then reboot. The deleted files will be recreated and you should be good to go.
I have done so, and now we wait.
Has anyone tried this fix to stop the name changing?
http://ispire.me/computer-name-changing-constantly-yosemite/
I'm a little nervous about changing the discoveryd .plist file. But nothing else I've tried has worked. It seems like it's getting worse. I could delete com.apple.preferences.sharing.plist and go a few days between ghost appearances, but now it's happening all the time.
My Mac Mini was up to (10), with all of the ghost mac mini's showing up in the Finder sidebar, until I replaced my 1st generation Time Capsule with a 6th Generation Time Capsule for an unrelated reason. I'll need to check to see if the issue has started again with the new router.
I'll try that, thanks. "Wake on Network Access" never seems to work for me anyhow; I assumed this would allow me to access media from iTunes on the Mac Mini from the Apple TV in my living room without first having to go upstairs and manually awaken the Mini, but apparently "Wake on Network Access" has nothing to do with waking on network accessI've found on a couple of installations, Release 10.10 and 10.10.1 Seed Beta 2. If I turn off "Wake on network access", restart the Airport Extreme, rename (delete (2)) the host. Everything works fine, except of course I can't wake the machines.
I'll try that, thanks. "Wake on Network Access" never seems to work for me anyhow; I assumed this would allow me to access media from iTunes on the Mac Mini from the Apple TV in my living room without first having to go upstairs and manually awaken the Mini, but apparently "Wake on Network Access" has nothing to do with waking on network access
Give the 5GHz network a different SSID (e.g. "network2") from your 2.4GHz network (e.g. "network"), then tell your MacBook to connect to "network2" and the rest of your devices to connect to "network." You do this by clicking the "Wireless options" button under the "Wireless" tab of AirPort Utility (assuming you're running an Apple router).I'm regards to the 5ghz network... I've recently moved into a townhouse and was getting really weird results over wifi (dipping bandwidth) after realizing that there are 30+ other wifi routers around me that were interfering with my wifi "wave" I discovered the wonders of the 5ghz network! Since having dual bands on for wifi printer, damn thing is only 2.4ghz#.. I have noticed this network naming and it's frustrating to see the duplicate macs on the network and time machine backups failing. This is the first time I've used dual networks and its a pain!!! But with everyone saying this is a Yosemite only bug might need to rethink what there change to network might have...
Is there a way to only have the MacBook running on 5ghz?
Give the 5GHz network a different SSID (e.g. "network2") from your 2.4GHz network (e.g. "network"), then tell your MacBook to connect to "network2" and the rest of your devices to connect to "network." You do this by clicking the "Wireless options" button under the "Wireless" tab of AirPort Utility (assuming you're running an Apple router).
I wasn't implying that it would; I was answering the previous poster's question about how to get only one of his devices to join his 5GHz network. Sorry, it was a bit off-topic...I have a 2.4 and 5 GHz network with different IDs, and this does not solve the problem either but it should help with network congestion.
What worked for me was turning off wake for network access under Energy Saver in System Preferences.
Then I edited that field and removed the numbers and such. Everything has been fine since I did that a couple of weeks ago. Before I had about 5 or 6 MacBook Pro (2), or (3) etc... Showing in Finder.
Rather than turning off DHCP on your router, couldn't you just simply assign a static IP address to the misbehaving Mac to achieve the same results? That way you could continue to use DHCP with all of your other devices yet see if this solution works for the renaming issue on your Mac.Hey, we should have a contest, I was up to (20) this morning!
I also saw that I had gone through a slew of IPs, so I'm trying this: I've turned off IP address through DHCP (I have an Airport) and assigned this computer a static IP.
We'll see how it goes, one downside is that the Airport no longer gives the hostname but rather the IP address, but I'm generally fine with that.
This may be what pushes me to drop DHCP entirely.
Hey, we should have a contest, I was up to (20) this morning!
Several weeks now and I'm still good with what I did. Nothing has come back.
Rather than turning off DHCP on your router, couldn't you just simply assign a static IP address to the misbehaving Mac to achieve the same results?
I'm up to 28 here
I did that a couple of weeks ago (turn off wake for network access) and everything was fine until yesterday when I was up to (20) and my IP address had also increased also in very similar numbers, leading me to think that perhaps this is linked to DHCP...
Sorry I wasn't clearer, this is exactly what I've done. When I mentioned I had an Airport, it was just to mention the type of AP that I have.
We have a new leader!
What do you mean your IP address has increased too?
It went from an assigned 198.162.1.5 to 198.162.1.22. DHCP lease time is on the order of days, and I don't have anywhere close to that many devices.
Seemed to be an interesting jump that should not have occurred, I noticed it at the same time I saw the (20) in the computer name. I know it may not be related, but it seems awfully coincidental...
Also potentially interesting is that my wired computers haven't ever had a problem with this. Only my laptop has this issue. All are on Yosemite.
I tried all solutions of this thread. Only this one worked permanently (for me)