LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   TightVNC on Slackware 12.2 ??? (https://www.linuxquestions.org/questions/slackware-14/tightvnc-on-slackware-12-2-a-699603/)

phys 01-25-2009 11:45 AM

Quote:

Originally Posted by Ilgar (Post 3420643)
I don't quite get what the problem is -- you use the user@ip format regardless of whether it's a LAN or internet connection. In your case you have 2 computers on the same LAN.

To have X forwarding, the ssh server (i.e. the one on the target computer) must be configured to allow X11 forwarding. This you do by modifying sshd_config. To see how it works, you may even test it on your computer by connecting to localhost (i.e. ssh user@localhost).

I have tried SSH with X11 forwarding between two Linux machines yet. I was able to successfully run a graphical program installed on target machine. Thank you very much Ilgar for your help and patience. :) So that I have learned relation between "IP Adress" and "Domain Name". Is it possible to have full desktop access by using SSH method?

phys 01-25-2009 12:03 PM

Quote:

You may also consider connecting to vnc through an ssh tunnel. Along the lines:

Code:

ssh -L 5900:localhost:5900 user@<your_home_machine>

and then connecting:

Code:

vncviewer localhost:5900

I hope I haven't muddied the waters for you, just providing options.

cheers,
Thank you mrclisdue;
You say that tunneling through SSH is more secure than using VNC alone? Actually I want to have full desktop access on target machine. I tried TeamViewer but it works only between two Windows machines and from Linux to Windows. I could not establish connection between two Linux machines using TeamViewer. I do not know whether TeamViewer is more secure than TightVNC or not, but I had just only tried it. I felt that TeamViewer is a bit faster than TightVNC. Alien Bob also said that VNC was insecure between two external machines. Now I am going to try SSH tunneling.

Ilgar 01-25-2009 12:26 PM

If SSH tunneling can be used to secure the traffic out of a port, then you can also try to apply that to XDMCP. A client connecting to a remote XDMCP server is like a terminal, that is, you get a login screen etc. as if you're sitting in front of the remote computer. XDMCP is also insecure, so you need some precautions like ssh to use it safely. XDMCP is enabled from the login manager of the target computer (KDM, GDM etc.). On the client computer, when you get a login screen, you can make the login manager scan the LAN for XDMCP servers for example. I don't know how to reach out-of-LAN XDMCP servers but it shouldn't be too hard.

Edit: From ssh + x11 I can run "startkde" for example, to start kde but it messes up my desktop. I don't know if it would be possible to run all that so that it's contained in a window, as in VNC.

Alien Bob 01-25-2009 12:57 PM

Quote:

Originally Posted by Ilgar (Post 3420837)
rom ssh + x11 I can run "startkde" for example, to start kde but it messes up my desktop. I don't know if it would be possible to run all that so that it's contained in a window, as in VNC.

For that you should try NX. NX is a technology based on modified X.Org, smart caching and ssh tunneling that displays a remote full desktop on your screen with sufficient responsiveness even over low-bandwidth, high-latency connections.
See http://nomachine.com for NX Server (partially closed-source), and see FreeNX (http://freenx.berlios.de/) for a fully open source solution based on the free bits of NX.
I have packages for freenx and the nx core libraries here: http://www.slackware.com/~alien/slackbuilds/freenx/

Eric


All times are GMT -5. The time now is 10:00 AM.