Yosemite [erroneously] displays multiple Shared Instances under Finder

Hello Bert Bassett

Interestingly when I upgraded to OS X 10.10.1, I still had the erroneous iMac multiples in the shared folder for about a week or so afterwards; they have since disappeared and not come back! (Fingers crossed!). However, I have also noticed that I too have the spinning beachball more frequently, streaming video crashes, hanging windows and the general performance is not as fast - with a large fusion hard drive and 32Gb of RAM in my iMac, it raises an eyebrow.

This thread solved the issue for me!

The problem started occurring while I had Yosemite beta versions installed.

It no longer seems to happen. To fix it for me, I needed to do two things (as people have previously mentioned):

1) reboot my router (which is an Airport)

2) On my mac, go to Settings --> Sharing and rename my computer back to what I wanted it to be (i.e. without the number in parentheses at the end)

I had done (2) a long time ago, but the extra computers never went away from my finder. After doing (1), they are finally gone. Yay!

OK... I did this, went into Sharing and re-named the iMac correctly after doing a 30-Second power down on my Airport Extreme AC and yes, the parenthesis are now gone. I read elsewhere that the number in the name is supposedly a problem in Yosemite where if you lose network connectivity and then reconnect the machine's name gets duped, so the number appears. What I'd like to know is how you "lose network connectivity" when the iMac is on 24/7, has an active working battery backup and I know we haven't had any power outages. On this one... I'll sit back and report in if I have any re-occurence of the problem. Thanks for the tip, I do hope its a good solid fix.

Now if somebody would just help me out with my _other_ thread concerning the spinning beach ball and sluggish opening of web pages in Safari.

Mike

I've had this since I installed Yosemite at release date. Ignored it until kids came home for Christmas and could not access the printer connected to my iMac for sharing on the home network. Not using an Apple modem/router. Ugh. This is like troubleshooting Windows, the reason I moved to Apple in the first place.

I'm posting this reply because I always come to this forum for solutions and it's a fantastic community - but it's my first post and in spite of working with databases for a living, I am not particularly technical. Looks like this may be a non-issue at this point, but figured it was worth sharing in case anyone else out there is looking.

We had this exact issue as well and just got off the phone with Apple support who were able to resolve it for us. We are running Yosemite 10.10.1 with a Time Capsule and 2 Airport Expresses.

As indicated earlier in this thread, it iwas an issue with Bonjour, Yosemite and Time Capsule - at least, it was for us - though, the technician also suggested that updates on the server side from our service provider might also trigger this behaviour.

I'm paraphrasing here, so apologies in advance, but in a nutshell what we were told is that there is a bug in the version of Bonjour in Yosemite, and the Time Capsule thinks that each refresh is a new computer and tries to esstablish a new IP address as a result.

The technician suggested we re-boot our Time Capsule, which we did - problem solved instantly.

Hope this is helpful to some of you out there who are still wrestling with this problem.

That solved the problem for me. Thanks!

Rebooting the Airport Extreme works. That eliminated all of the past list of server names. Thanks for the advice.

I did both and neither did the job.

This worked for me, and I didn't need to kill my finder preferences, just the first 2 steps.

Thanks for the solution.

My duplicate entry in finder has gone away. I don't think it was related to the Yosemite bug others have been encountering. I recently took a Windows laptop out of service because I had bought a newer one. I gave the new computer the same name as it's predecessor. My Mac Mini retained a memory of the other computer for a few days but has now forgotten it.

Thx - worked also for me. Step 4 was'nt required.