Can't control Lion macmini with ARD 3.5.1 client

You know airdrop is only compatible with select machines, so I wouldnt rush to reinstall if yours isnt on the list.

Nothing that Lion Cache Cleaner did could make ARD work on computer #3. However, it is clearly software related because when I booted from a flash drive with a fresh install of Lion, it worked fine. The client software is 3.5 with a fresh install.

I will try Onyx to see if that helps. I may also try updating the client software on my flash drive to see if 3.5.1 breaks the connection or not.

A solution to this problem (via Terminal commands) has been posted here:

https://discussions.apple.com/thread/3191199?start=15&tstart=0

NOTE: there is a space in the word "kickstart" that should not be there. If you copy and paste the commend directly from the post it will fail unless you remove the space in "k ickstart"

This solution worked for me and many others.

Thanks. That worked for computer #3. (My other two were fixed by running Lion Cache Cleaner.)

Mocha VNC App has now been updated to allow Lion authentication during VNC negotiation phase. I have now updated to ARD 3.5.1 and all is well from iPhone.

If you're still having an issue, this will fix it:

https://discussions.apple.com/thread/3289794

This worked for me to. I had the same problem when Lion came out and ARD was upgraded.

Notes to remember:

1. If possible turn off the remote management and remote sharing off the client computers before upgrading

2. Perform the upgrade

3. Switch them all back on again

If you have this problem after the upgrade, just do as tmassa01 wrote and switch them all off (uncheck them) and check them back on again.

This worked on 4 of my clients.

Worked perfectly for me (with the space between the 'k' and 'ickstart' removed 🙂

Thanks this fixed, my problem.

I seriously thought this answer was dumb but i tried it anyways!! AND IT WORKED!!

Unchecking and checking it really did work.

Thank you

I've had the same problem, but did'nt solve with deactivation and reactivation of screensharing. Then I noticed that the server name in the windows title bar was followed by a (2).

I realized that both network cards, ethernet and airport were activated and my desktop sharing app was unable to correctly connect to the server.

I managed to deactivate airport via ssh ant that did the magic.

Everithying up'n running.

I hope it could help.

The kickstart command through ssh is not working.. Still no VNC or ARD visuals..