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


Click here to return to the 'How to securely control another Mac over the internet' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
How to securely control another Mac over the internet
Authored by: leturner on Jan 10, '06 07:54:25PM

I know this post has gotten stale but it's a great hint ... that unfortunately I can't get to work.

I've got exactly the situation described in the hint: Mom with Mini, me with G4 laptop, both behind routers. I've followed instructions to the letter (triple checked) including the changed password requirement with the 2.2 ARD update. But I'm getting stuck at the reverse tunnel stage.

When she clicks on the .term file, terminal launches runs the ssh script, then sits there a bit and times out.

I have:

- updated ARD on mini to latest (2.2)
- gotten the virtual static IP address
- Created the terminal script file
- Turned on ARD in the mini
- forwarded port 22 on my airport express to the 192 IP address of my laptop (public port 22, 192.168.1.x, private port 22)
- opened port 22 on my software firewall

I've run a copy of the .term file from my own laptop, and it appears to work - asking for my dummy account password - and I get into myself. But is that really a test since I'm connecting to myself? It's not clear to me if when i do it whether or not I actually go out and back through the router and the port forwarding works.

Any suggestions would be greatly appreciated.

Thanks



[ Reply to This | # ]
How to securely control another Mac over the internet
Authored by: dcoyle on Jan 28, '06 06:46:01PM

I've been playing around with SSH a little, including this hint which I ultimately got to work. I'm no expert (far from it), but what I found really useful was using Console to see what gets logged - look on both machines. In my case, I had to delete, then re-create keys in /etc. I don't believe they are used at all, but sshd won't work without them.

Not saying I think that's your problem, but there appear to be a lot of things that can go wrong. The copious logging is one of the things I really like about OS X and will get you pointed in the right direction. I hope that someone who actually knows what he is doing reads your post and can help you.



[ Reply to This | # ]