-
All replies
-
Helpful answers
-
Oct 23, 2013 8:49 PM in response to Not_Soby alicantemacman,Im having the exact same problem, a mac mini running 10.8.5 server, i put ard 3.7 on it to control 10.9 machines, after it rebooted i can no longer control it. I can send commands to it via ard, but thats it. Going to try this, thanks
-
Oct 24, 2013 1:45 AM in response to Not_Soby David MacDonald2,I also have this problem on a network of about 28 Macs. Upgraded to ARD 3.7. Running 10.8.5.
Most Macs are accessible via ARD as always, but some fail exactly as you describe. If the firewall on the client is disabled then ARD can access the remote machine OK.
This looks like a flaw in ARD 3.7 to me.
Have not yet upgraded any Macs to Mavericks.
-
by alicantemacman,Oct 24, 2013 1:59 AM in response to David MacDonald2
alicantemacman
Oct 24, 2013 1:59 AM
in response to David MacDonald2
Level 1 (4 points)
Servers EnterpriseYep its the firewall alright, can now access the 10.8.5 server again. They need to fix this fast
-
Oct 24, 2013 2:03 AM in response to Not_Soby Not_So,I should add that the Mac Mini is the server hardware model, running the 10.8.5 client version of OSX ML. Not sure if this makes any difference!
-
-
Oct 24, 2013 2:25 AM in response to Not_Soby joeblowjapan,Same problem here on a MacBook Air, same workaround fixes it. Bummer.
-
Oct 24, 2013 3:04 AM in response to alicantemacmanby David MacDonald2,I think I have a solution/workaround that allows the firewall to be ON.
On the client machine, go to firewall options, scroll though the list and look for screensharingd.
Make sure it is set to Allow incoming connections.
Turn the Firewall OFF.
Restart the client Mac.
When restarted turn the firewall ON again. At this point I was asked if I wanted screensharingd to allow connections (even although I had already set it to do so), and so you may have to set this option a second time.
Now try ARD from the adminstrator Mac. This worked for me, and allows remote management with firewall ON.
I hope this helps: interested to see if it does.
-
Oct 24, 2013 3:05 AM in response to David MacDonald2by Not_So,Does this workaround still stick / work if you reboot the client mac again with no other changes? I tried so many different options last night I lost track of what I had tried, but one common feature was that none of the options worked for further reboots.
-
Oct 24, 2013 3:18 AM in response to Not_Soby alicantemacman,yep, Ive rebooted mine several times to test, still there
-
Oct 24, 2013 3:20 AM in response to alicantemacmanby Not_So,Great - I'll try when I get back from work and report back!
-
Oct 24, 2013 4:10 AM in response to Not_Soby David MacDonald2,Unfortunately, it doesn't appear to work after a reboot for me.
I think all I have achieved is a way restoring ARD access with the client firewall ON, but only for that particular session. Even when using the padlock on the firewall tab to prevent further changes, screensharingd reverts to Block incoming connections. You would have to reset this each time, which is hardly ideal.
-
Oct 24, 2013 6:58 AM in response to Not_Soby Dan Smit,Here's a bandaid until Apple figures out what exceptions to add to the firewall
https://discussions.apple.com/message/23490652?ac_cid=tw123456#23490652
-
Nov 2, 2013 6:57 AM in response to Not_Soby Angus Anderson,Hi
Just opened up firewall unlicked it and in advanced screensharingd was set to block incoming connections sett to allow Ok'ed and ARD now has control after multiple re-boots. seems to all be good. Not sure whey screensharingd needed to be turned on as under ML i assume it was off and ARD worked fine.
-
Nov 2, 2013 1:41 PM in response to Angus Andersonby David MacDonald2,Does it continue working after you restart?