AppleDane
Level 1 (0 points)

Q: screen sharing broken again after update to 3.7 without Mavericks upgrade

I did the standard updates tonight - which included a remote desktop update (to version 3.7 I think) - the ARDagent.app in the System -> LIbrary -> CoreServices -> Remote management folder.

 

After the update (I'm still running Mountain Lion) - screen sharing doesn't work with any of my other Macs in the house.  It basically sits there and never connects - saying "connecting to...." - similiar to what it did a long time ago after the 3.6 updates from 3.5.  Eventually it gives this error... "connection failed to ..."  and "Please make sure that Screen Sharing (in the Sharing section of System Preferences) is enabled on the computer to which you are attempting to connect. Also make sure your network connection is working properly."

 

I have already tried to restore that folder from time machine to version 3.6.2, as well as restored the screensharing.app file to the older version, but to no avail.  Have already rebooted all the machines, restarted my airport, network hubs, etc.  Tried stopping and restarting sharing already as well.  No go on any option.  Was working just fine before the updates tonight.

 

Any one else have similar issues and know how to fix?

 

Thanks.

OS X Mountain Lion (10.8.5), Screen sharing not connecting

Posted on Nov 6, 2013 10:09 AM

by PeeDee768947385,Solvedanswer
PeeDee768947385 PeeDee768947385
Level 1 (14 points)
Mac OS X
A:

"Downgrading my client to 3.6.2 solved the issue."

 

Sorry dandeliondigitalI wasn't more explicit, but was following a range of suggestions earlier in this thread though I read so many on this problem I lost track. I'm running a headless mac mini server, OSX 10.8.5 on both the client iMac and the server.

 

First, I had to hook up a screen and keyboard to the mini. I then verified that it was the firewall bug discussed in this forum by screen sharing with the server firewall off. I then turned screen sharing off in preferences, and removed the "screenshared(?)" line entirely from the firewall using the minus button.

 

Then, on the server I moved the contents of the folder "/System/Library/CoreServices/RemoteManagement/" to the trash. I then searched up and downloaded the 3.6.2 version of this file: "RemoteDesktopClient.dmg". Running the install pkg inside that file reinstalled the earlier version.

 

Finally, I turned "Remote Management" on in the preferences pane (but I think "Screen Sharing" would do) and "Enable screen sharing" in the Server Settings pane.

 

Restarted the firewall in Preferences Security.

 

I probably restarted the server after each of these steps.

 

Still working for me today. Good luck.

Posted on Nov 2, 2013 3:53 PM

Close
AppleDane

Q: screen sharing broken again after update to 3.7 without Mavericks upgrade

  • All replies
  • Helpful answers

first Previous Page 8 of 8

  • by ckeilah,

    ckeilah ckeilah Sep 4, 2014 1:54 PM in response to AppleDane
    Level 1 (12 points)
    Mac OS X
    Sep 4, 2014 1:54 PM in response to AppleDane

    I solved this problem by rebooting the client machine and NOT logging in locally, but by connecting from the remote ARD, and logging in from there.  ARD/ScreenSharing seems broken though, and has been for a while now--not sure if this is new with Mavericks or even before.  Anyway, hope this helps someone.

  • by jcv,

    jcv jcv Dec 18, 2014 6:06 PM in response to AppleDane
    Level 2 (425 points)
    Dec 18, 2014 6:06 PM in response to AppleDane

    Yikes. Thanks for this.

     

    I'm having the same problem after upgrading to Yosemite-- all sharing settings set up properly etc.

     

    Turning off the firewall fixed it (and like everyone else, the FW was set to allow all appropriate connections). I have more than one hardware firewall and this is a media server (only) so I'm not too concerned about it.

     

    What a pain, though. Now if only I could figure out why Bluetooth is ridiculously slow and disconnects all the time on the same machine. It was working beautifully before the "upgrade"- ugh. Zapping PRAM didn't fix it.

first Previous Page 8 of 8