AppleDane

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

Close

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

  • All replies
  • Helpful answers

first Previous Page 6 of 8 last Next
  • by RogerGP,

    RogerGP RogerGP Nov 23, 2013 7:03 AM in response to AppleDane
    Level 1 (0 points)
    Nov 23, 2013 7:03 AM in response to AppleDane

    Hello. This works for me today to solve the problem about the error message "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."

     

    In the mac I want to control remotely:

     

    • Go to System Preferences
    • Sharing
    • Unselect File Sharing, Remote Login and Remote Management
    • Restart the computer
    • After restart, Select again the option in step 3.

     

    Now I can access that computer from my Apple Remote Desktop.

     

    Versions:

     

    Apple Remote Desktop: 3.7

    OS X: Mavericks.

  • by irob_swe,

    irob_swe irob_swe Nov 27, 2013 5:02 AM in response to RogerGP
    Level 1 (5 points)
    Nov 27, 2013 5:02 AM in response to RogerGP

    This is usually the best medicament to ard-patients with a bad hearing:

     

    sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -activate -configure -access -on -privs -all -allowAccessFor -allUsers -restart -agent -verbose
    

     

    Oh, and with remote login enabled at the client that command save you if you are lazy or offsite as you can login via ssh and use it

  • by RogerGP,

    RogerGP RogerGP Nov 27, 2013 5:53 AM in response to irob_swe
    Level 1 (0 points)
    Nov 27, 2013 5:53 AM in response to irob_swe

    Hello irob_swe

     

    Thank you very much for your advice. It works perfectly

     

     

    Bes regards

  • by walter.dufresne,

    walter.dufresne walter.dufresne Nov 27, 2013 6:12 AM in response to AppleDane
    Level 1 (0 points)
    Nov 27, 2013 6:12 AM in response to AppleDane

    FWIW, I have six Mountain Lion machines that displayed the Screen Sharing error message.  For me, Roger GP's solution only worked until the next reboot.  Last week I cloned and upgraded the least-used, non-production MacMini (it mostly does telephony) to Mavericks, and Screen Sharing works again, through reboots.  Yesterday, I cloned and upgraded the next least-used MacMini (it watches a Promise Pegasus array) to Mavericks, and Screen Sharing works again, through reboots.

    I've stopped upgrading for now, and will watch the two Mavericks machines for future trouble.

  • by irob_swe,

    irob_swe irob_swe Nov 27, 2013 6:36 AM in response to walter.dufresne
    Level 1 (5 points)
    Nov 27, 2013 6:36 AM in response to walter.dufresne

    Woha, sorry for the off topic but that was a very dangerous move to upgrade that system. ARD might be your least problem right now...

    Beware walter.dufresne you might have a ticking bomb there with Pegasus on the OSX 10.9!!!

    If you ever have had any WD disk attached there might be a risk you also have their software and that can format the whole Pegasus array in an instant. You might very well lose every file you have and it's irreversible.

     

    WD has removed their software from their web and are investigating what happens and what disks are in risk zone but fact remains - Pegasus owners lose data every day at the moment as they find out the Pegasus is actually that empty volume named "MyBook". Remove any daemon named wd asap.

  • by walter.dufresne,

    walter.dufresne walter.dufresne Nov 27, 2013 6:33 AM in response to irob_swe
    Level 1 (0 points)
    Nov 27, 2013 6:33 AM in response to irob_swe

    I know, I know, Mavericks is currently an unreliable solution.  Thanks for the alert.  I'll keep a sharp eye on the Minis.  (FWIW, the Pegasus array is backed up to another Pegasus off-site, and there's a week's worth of work I need to train-net from one site to another.)

  • by irob_swe,

    irob_swe irob_swe Nov 27, 2013 6:39 AM in response to walter.dufresne
    Level 1 (5 points)
    Nov 27, 2013 6:39 AM in response to walter.dufresne

    Great, just hope you don't have two MyBooks then if you updated that system to 10.9 at the same time.

    If you gonna do it - do it properly! ;-)

  • by enigmakv,

    enigmakv enigmakv Nov 27, 2013 11:56 AM in response to irob_swe
    Level 1 (0 points)
    Nov 27, 2013 11:56 AM in response to irob_swe

    OOPS.  Not for me!

     

    I tried this terminal trick on my 2012 Mini, Mtn Lion (10.5.8).  I did a copy and paste of the entire command and got the full verbose feedback with no errors reported.

     

    No luck with Remote connection.

     

    Even tried a reboot...still no luck with Remote connection.

     

    irob_swe wrote:

     

    This is usually the best medicament to ard-patients with a bad hearing:

     

    sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -activate -configure -access -on -privs -all -allowAccessFor -allUsers -restart -agent -verbose
    

     

    Oh, and with remote login enabled at the client that command save you if you are lazy or offsite as you can login via ssh and use it

  • by irob_swe,

    irob_swe irob_swe Nov 28, 2013 3:36 AM in response to enigmakv
    Level 1 (5 points)
    Nov 28, 2013 3:36 AM in response to enigmakv

    This is why you should skip refering to your OS by name - I guess you have 10.5.8 (which has another stupid cat name) so here is a command you can use with that OS to see if the ARDAgent is running on your system:

     

     

    ps -x | grep [A]RDAgent

     

    Enable File Sharing and try to connect to your computer over AFP. If you find the computer in the Network folder in the Finder and you open that you should have both "Connect as..." and "Share screen...".

     

    If ARDAgent is running and you have all the settings from the command I sent in the other post I'd say you must take a look at your firewall in the Security pane of System Preferences or start looking if the pesky app called Little Snitch is there somewhere.

  • by geychaner,

    geychaner geychaner Dec 2, 2013 9:47 AM in response to AppleDane
    Level 1 (5 points)
    Dec 2, 2013 9:47 AM in response to AppleDane

    I ran into the exact problem described here trying to get Back to my Mac working with Remote Desktop 3.7.0 on OS X 10.8.5. I solved it by eliminating Remote Desktop 3.7.0 as follows (after downloading the installer and getting the file list it installs by running it and using Show Files):

     

    sudo rm -rf /Library/Application\ Support/Apple/Remote\ Desktop/Notify

    sudo rm -rf /System/Library/CoreServices/Menu\ Extras/RemoteDesktop-Lion.menu

    sudo rm -rf /System/Library/CoreServices/Menu\ Extras/RemoteDesktop.menu

    sudo rm -rf /System/Library/CoreServices/RFBEventHelper.bundle

    sudo rm -rf /System/Library/CoreServices/RemoteManagement/ARDAgent.app

    sudo rm -rf /System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle

    sudo rm -rf /System/Library/CoreServices/RemoteManagement/ScreensharingAgent.bundle

    sudo rm -rf /System/Library/CoreServices/RemoteManagement/screensharingd.bundle

    sudo rm -rf /System/Library/LaunchAgents/com.apple.RemoteDesktop.plist

    sudo rm -rf /System/Library/LaunchAgents/com.apple.screensharing.MessagesAgent.plist

    sudo rm -rf /System/Library/LaunchAgents/com.apple.screensharing.agent.plist

    sudo rm -rf /System/Library/LaunchDaemons/com.apple.RFBEventHelper.plist

    sudo rm -rf /System/Library/LaunchDaemons/com.apple.RemoteDesktop.PrivilegeProxy.plist

    sudo rm -rf /System/Library/LaunchDaemons/com.apple.screensharing.plist

    sudo rm -rf /private/etc/com.apple.screensharing.agent.launchd

     

    and then installing the Remote Desktop 3.6.2 package from http://support.apple.com/kb/dl1594. Definitely a bug.

  • by merced317,

    merced317 merced317 Dec 4, 2013 3:11 AM in response to AppleDane
    Level 1 (0 points)
    Dec 4, 2013 3:11 AM in response to AppleDane

    Apple Remote Desktop 3.7.1 is out.

     

    http://support.apple.com/kb/HT6045

     

    One of the fixes is:

    • Prevents an issue that could cause the OS X Firewall to block Remote Desktop connections. See Additional Information below.

     

    The Additional Information is:

    • If you previously updated a Remote Desktop client to 3.7 and lost access to it because of the OS X Firewall service, restart the client computer after installing the 3.7.1 update. The correct firewall rule will be automatically added, and you will be able to connect to the client via Remote Desktop.

     

    I can confirm that I have installed this on my 10.8.5 system, restarted, and it works!  I'm glad to see Apple fixed the problem.

  • by SMJ NY,

    SMJ NY SMJ NY Dec 4, 2013 12:54 PM in response to merced317
    Level 1 (0 points)
    Dec 4, 2013 12:54 PM in response to merced317

    FYI --

     

    3.7.1 finally solved my issue when installed last night.  Multiple reboots on my Mac Mini, and working as expected.  Been spending the past month or so constantly bringing down/up the firewall to access.  Been a real pain but happy it's now working.

  • by Mac.Y,

    Mac.Y Mac.Y Dec 4, 2013 6:39 PM in response to SMJ NY
    Level 1 (0 points)
    Dec 4, 2013 6:39 PM in response to SMJ NY

    On my iMac and Macmini with OSX 10.7.5, ARD 3.7.1 does not work correctly.

    The problem is exactly the same as 3.7.

  • by XFox,

    XFox XFox Dec 5, 2013 12:11 AM in response to Mac.Y
    Level 1 (90 points)
    Dec 5, 2013 12:11 AM in response to Mac.Y

    Mac.Y wrote:

     

    On my iMac and Macmini with OSX 10.7.5, ARD 3.7.1 does not work correctly.

    The problem is exactly the same as 3.7.

    Did you reboot the Macs?

    It works here.

  • by Mac.Y,

    Mac.Y Mac.Y Dec 5, 2013 12:15 AM in response to XFox
    Level 1 (0 points)
    Dec 5, 2013 12:15 AM in response to XFox

    Yes, I did several times.

    But not changed.

first Previous Page 6 of 8 last Next