Upgraded to Yosemite and can no longer remote into my work iMac through screen sharing- it is turned on in settings?

Just an update. By deleting all the BTMM entires in key chain as well as all those associated with the remote computer, my systems have been able to remote in successfully for the last 24 hours without interruption. The only hiccup is one of my computers I cannot get btmm working but I CAN login using adminstrator privileges, i.e. just a user login. Not sure why for this one particular computer combination (i.e. older Mac with relatively new Mac does not allow BTMM but old Mac with slightly old laptop air will). Once again I can login remotely to all three computers I have so it works now. If for some reason it stops working again I will update this community but once again deleting all the BTMM and the lines related to the remote computers in keychain appeared to work

I think that this problem is not just the screen sharing but a problem with the networking stack in Yosemite, my (late 2009) Mac Mini running Yosemite was showing all sorts of issues, with frequent disconnections to the internet and local network. I rebuilt the Mac Mini as Mavericks and my issues seem to have resolved.

hello

I had the same problem but I think I have resolved !

I downloaded Titanium Onyx free software for Yosemite.

I erased all system caches and restarted.

Now I can again share the screen !

I hope it will stay like this.

Hi,

I spoke too soon. Screen sharing is now a random off/on event, with no apparent rhyme or reason.

Tried the system cache thing (using Cocktail) without success.

Logging onto the remote macmini hard disk occurs instantly but no such luck with screen sharing, (whether I do it via the GUI or by putting in the local network IP)

Back to the drawing board

Cheers

Iain

hello

the emtying of cache didn't really resolve the problem.

It is like you say, sometime on, sometime off, sometime I can see the files by filesharing but I can't share screen.

sometimes computer re-ask me my session password ( he knows it !) but he says that it is bad.

On the Yosemite machine we have several sessions in our home.

When on Yosemite computer this is not my session, but my wife's session I have to connect with her session.

Since 20 years I know Apple and this was always working. they broke this feature, I don't know why.

Before they thought for people and perfect operability, perhaps now they think for money only and get stupid. :-(

If you find something, let me know. On waiting for solutions I put a dropbox to the two machines, this get me more independent of networking...

cheers

Hmm,

maybe this is more complex.

Tonight trying to play a downloaded TV show from my Macmini on the TV screen that its connected to. Got a message that the machine wasn't authorized, then put in my apple ID and password and the dialog box said that the machine WAS authorized but the movie wouldn't play.

Then set screen sharing to off (this is said to be a fix for the 'this display can't show HDCP content' error. The re-enabled screensharing and the iTunes episode played OK and now screensharing from my MBP works OK again, (temporarily I'm sure)

Whether these are connected or not I'm not sure...seems a bit of a mess anyway.

Cheers

Iain

Bonjour (?) helloo

it seems (I read about) for me that Apple wanted to re-write this feature in a new way, because they had only evolved the heritage systèm from beginning of OSX and world have changed...

I liked a lot these privat systèms "Bonjour". This was a simple privat feature. From outside I looked with VNC to it.

This should have stayed in the système as a subfeature of their new bigger vision.

Are there visionners today ?

have a good day

It's really not complex at all. YoShitOnMe broke the Bonjour Sleep Proxy and the Screen Sharing, Home Sharing or Mac Falling of the home network are all related. Until the Sleep Proxy is fixed this will not go away. Work around is leave the mac on 24/7.

The location of the Screen Sharing application is in the following locations:

• Yosemite

  /System/Library/CoreServices/Applications

• Mavericks

  /System/Library/CoreServices

My Screen Sharing app is parked in my Dock.

I am serving the screen of my 2014 MacBook Air with 10.10.2 via vnc to a 2011 Mac mini with 10.9.5. There are two stages of sleep that occur when facing the monitor on the mini. The Air VNC screen will begin to fade to sleep. At this point, a mouse click on the Air's VNC screen will prevent sleep. If however, the Air fully falls to sleep, there is no waking it from the Mac mini — one must click the physical Trackpad on the Air, and enter (in my case) a password to wake it. It is then available on the mini again.

Similarly, I have the Air configured to require a password to login. Unless I am logged in to the Air, the Screen Sharing Host prompt on the mini, will not connect to the Air, and throws a dialog about that.

Other ways to connect to a vnc shared machine:

• In the browser

  vnc://host.local

• Finder's Connect to Server…

  vnc://host.local

Just another 2 cents here, I thought everything was fixed. That is, I made sure that I cycled through the iCloud BTM information such that it cleared out old information. My machines were all cooperating and I could remotely login whenever I wanted. The only time that a hiccup occurred, is when I remotely logged in BTMM, and I forgot to eject the remote desktop. When I forgot to eject the remote desktop, this prevented me from ever logging back in remotely no matter what I tried, i.e. including vpc. Also today, I am in San diego, logged in and also ejected the remote system. However NOW I cannot login again so bottom line is I do not think this is fixed yet, i.e. cannot get back to my mac without driving back to the remote computer and cycling the BTMM settings. This sounds like an awful mess and would hope someone either figures out how to fix it or Apple fixes it. I realize now something is being stored in the remote computer preventing any additional login attempts, note my computer is on 24/7 so that is not the issue.

For those still following this feed, this turned out (for me) to be a simple solution after reading all the feeds, suggestions, fixes, Apple bulletins, etc. System Preferences>Security>Firewall Options>"allow" or "block" incoming connections. There are two related to Screen Sharing - the obvious "Screen Sharing" (pic #1 below) and a less obvious (pic #2 below) "screensharingd". Both have to be ticked "allow." I've been networking with to MBPr and my desktop iMac. Screen sharing worked in all directions except from the MBPr's to the desktop. This solved the problem.

Scroll down . . .

Simple . . . wished I'd figured this out long ago. Hope it works for you as well.

Rod

Thanks Rod! Works for me!!

Hello all.

I had problems accessing my mac pro remotely also and did some troubleshooting with the Tech Guru here in Charlottetown (very knowledgeable group of people!)

What they told me was to make sure that airport was turned off as I am connected hardwired through the ethernet.

This solved my issues and I can now log in remotely!

Regards

Stephen

SUNNY0523

That is simply a work around that is working for you and not a fix. My airport is turned on and I have no issues accessing the mac remotely.

No documentation says that is even a requirement. If the work around is working for you then thats is great but turning of the airport defeats the purpose of its functionality.

I have been seeing this very problem with .vncloc files created pre-yosemite and in yosemite. Now all of my mac's have names like "Mac Mini" and "Kathyrn's iMac" where there are characters that need URL encoding. So as I read through other people having the same problem I decided to figure out why some things work and others do not. So I found the existing .vncloc files I had created pre-yosemite and opened them up in vi to take a look.

There are two properties in the file one with name URL and the other with targetAddress and they are different.

<key>URL</key>

<string>vnc://Kathryn’s iMac._rfb._tcp.local</string>

<Dict>

...

<key>targetAddress</key>

<string>vnc://Kathryn%E2%80%99s%20iMac._rfb._tcp.local</string>

...

</Dict>

So this gets me thinking. I drop back to the command line and type

open "Kathryn’s iMac._rfb._tcp.local"

And it works. but

open "Kathryn's iMac.vncloc"

cannot find the host.

So I edit the .vncloc and start experimenting.

Once URL is set to a URL encoded string I can right click on the entry in the dock again and open it. BUT. Screen sharing edits the file and removes the encoding and puts it back to English readable and then the second time the .vncloc file no longer works. So I drop back to vi and edit again. This time I change permissions on the file on disk so it is not writable. chmod -w Kathryn\'s iMac.vncloc. Then the #&#@&!@ program leaves my URL string as I left it and it works every time. Of course now I cannot change settings - but at least it works.

So my guess is that there is a bug in Yosemite. Something like pre-yosemite used targetAddress and yosemite uses URL to and something still "repairs" the URL to english readable - and they are now incomparable. I would guess that anyne having this working has no need for URL encoding. And of course everything works from the command line just fine.

So thank you Apple for a marvelous new bug - still not fixed in 10.10.4 that I installed yesterday.

Moral of the story - don't put spaces and apostrophe's in your machine names even though Apple does this by default. And/or lobby Apple to fix this back to pre-yosemite behaviour that actually worked.