Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Manage multiple NATted Macs with Apple Remote Desktop' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Manage multiple NATted Macs with Apple Remote Desktop
Authored by: madamov on Feb 19, '08 08:50:34AM

Timbuktu used to allow, probably still allows, to remote control one machine within network and start Timbuktu on that machine to control computers within local networks, so you have session inside session. Last I tried that with ARD version 2 and it didn't allow it, I don't know if they changed it with version 3.

You can combine ARD and Timbuktu, have your parents install Timbuktu on all local machines, use ARD to get inside local network, then use Timbuktu to control machines on local network.

[ Reply to This | # ]
Manage multiple NATted Macs with Apple Remote Desktop
Authored by: RickoKid on Feb 20, '08 08:02:47AM

You can control ARD Admin using a remote Mac using ARD (piggybacking). You just need to enable the "Allow control of this computer when this application is running" option.

[ Reply to This | # ]
Manage multiple NATted Macs....CAREFUL!!
Authored by: rbenezra on Feb 20, '08 09:26:44AM

I have been doing this type of thing for years but warn that you should never open the ARD ports for security reasons. I would only open port 22 for SSH on my home network since the encryption with public and private keys is quite secure (Note I did have port 22 opened for me at work to do the reverse commute and one day there were 6000 hits per second (!!) on my machine from an ip address in China as someone tried unsuccessfully to get in to our network; if there are open ports protected with just a user id and password, they can get in at this rate with NO PROBLEM, and they will, probably just for fun).

So the set up is with Timbuktu which allows you to direct all traffic through a secure tunnel. You need to set up SSH on the home computers, know the IP address of the home server (if dynamic, you need a domain name, free these days through DynDNS), different static ip addresses on the home computers and a means to direct the traffic to a particular machine (SSH Tunnel Manager, also free, with a fairly simple set up allows you to direct traffic to any machine on the home network through the secure shell). I know it sounds like a lot but it really is quite easy and once set up, just works seamlessly. Post back if you need more help.

[ Reply to This | # ]