| Matthew Rosewarne on 17 Dec 2007 13:24:09 -0800 |
|
On Monday 17 December 2007, brent saner wrote: > i also agree; one of the great things about linux is with X forwarding > and just plain ssh tunneling (or even a simple ssh session), you can > resolve around 90% of problems they're experiencing, i'd guess. You'll probably have an easier time with NX. X11 forwarding is awesome, but becomes painful on slow links. It would also not possible to "mirror" her screen remotely without using something like x11vnc over ssh. Having used all of these methods, I've found NX to be by far the fastest and easiest to work with. I use the NoMachine packages, since FreeNX only comes as a tarball. They are capped at one user, but that's fine for remote troubleshooting. http://www.nomachine.com/download-package.php?Prod_Id=5 > as for dynamic IPs, definitely a potential problem. you can sign up for > an account at no-ip.org or dyndns.org (there is a client updater that > takes your current public ip and points the url you specify to the > public ip)... I do this with my desktop machine using ddclient, which is on startup and from cron. What I find to usually be more of a problem is the settings on the router (if you have one). Since at least my router forwards ports by IP, the occasional DHCP change will break everything, requiring me to update the rules for the new local IP. > i've also been told that one can use netcat to tunnel ssh traffic past a > NAT router without forwarding ports (to "repeat" traffic), but this is > something i'm still studying and looking into. I've not heard of that trick... It would need to be initiated from her end though. Attachment:
signature.asc ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|