2008/11/16 Kyle <[EMAIL PROTECTED]>: > Peter, > > for some clarification please. > > Peter Chubb wrote: >> >> On Linux, BSD, Solaris, MacOSX or other Unices that are running X >> locally, you do >> >> $ ssh -f -X host xterm & >> >> On the host you need to have >> X11Forwarding yes >> X11DisplayOffset 10 >> >> in /etc/ssh/sshd_config > > ## So to be clear on this; > > The 2 X11 params above are set in sshd_confing on the host I wish to control > (<controlled host>)? > > From a Linux box, I would issue your above command; and from an OSX host, I > can use the X11.app (which is I believe and Xterm application). Correct? > >> And providing you have xauth and xterm installed on the remote host, >> you should get a local terminal window, from which you can run >> anything you want. >> > ## So these need to be installed on the <controlled host>? > > >> You *won't* be able to run the window manager there (is that what you >> mean by `The gui' ???). It runs on your local machine. >> > > ## I can see the possibility for confusion here. > > To be clear; My initial question has to do with running the <controlled > host>'s desktop much like a VNC or RDP session. Which host it physically > runs on, I don't suppose I really mind too much. So long as I can have it > all running through std. corporately-available ports. > >> You should however be able to run anything else. >> >> The way this works is that clients on the host talk to the SSH proxy >> on that host which tunnels the protocol back to the display indicated by >> the >> DISPLAY variable in ssh's environment on yo > > ## But if I understand your post correctly, you're telling me how to connect > to a host and then run X-based applications displaying on my controlling > host, but which are actually running from the <controlled-host>?
Hey, Why not just use VNC over ssh? Crash course: Setup the vnc server on the linux box (system->preferences->remote desktop on Ubuntu) Then in the putty options add a port forward from an available port (e.g. '12345') to 'localhost:5900'. On your windows VNC client you then connect to 'localhost:12345' and it should connect to the remote VNC server. VNC might not be secure or run on the desired (corporate friendly) port, but forwarding it over ssh can help solve both of those issues... cheers, Owen. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
