Putty.exe vs. VNC vs. XWindows
Putty.exe vs. VNC Vs. X Windows??? Would anyone have any disadvantages or advantages of the subject above? Any thoughts would be very helpful? CONFIDENTIALITY NOTICE: This message and any attachments originate by electronic mail from Blue Cross of Northeastern Pennsylvania, First Priority Health, AllOne Health Management Solutions, Inc. and their subsidiaries/affiliates ("BCNEPA"). Both this document and any attachments are intended for the sole use of the addressee indicated above and may contain proprietary, privileged and/or confidential information. If you are not the intended recipient of this message, you are hereby notified that any use or disclosure of this information is strictly prohibited. If you have received this transmission in error, please notify the sender by reply email and delete the original message immediately. Thank you for your cooperation.
Zientek, Selene wrote:
Putty.exe vs. VNC Vs. X Windows???
Would anyone have any disadvantages or advantages of the subject above? Any thoughts would be very helpful?
They are all fairly different tools. Putty is the name of a program used for SSH access - this will only give you command line (CLI) access in itself, so if you want to run a GUI app on linux you'll need something else.[1]. Putty isn't the only program you can use for this either. VNC typically lets you connect to existing sessions. Some linux distros set this up so you can do remote-assistance type access, some set it up so you get a new login screen. VNC can be pretty slow, but you probably won't notice over a LAN. X lets you start applications on the remote system and display them locally. This could be a single application, such as an xterm, or firefox, or it could be your entire window manager/desktop environment, such as GNOME or KDE, including the login screen. X is similar in concept to RDP, the MS Windows Remote Desktop Protocol, although it is very different in execution. However, you can do the same things with them - export your entire environment, or just export a single application. There are also other technologies round, such as NoMachine NX, which is fundamentally similar in concept to X, but offers better performance. And there's tools like x2x, x2vnc, and synergy, which basically let you share a mouse and keyboard between multiple systems - eg, you can set it up so that if you scroll the mouse past the left hand side of the screen, it appears on the screen to your left, and you can control it there. This is useful if you have multiple computers with a screen each, but don't want to keep changing keyboard and mouse round. The real question is, what do you want to do? If you have a windows machine at your desk and a linux machine elsewhere and you want to run a full GNOME environment, I'd really recommend using X (look for notes on setting up a windows X server and XDMCP on your linux system). If you want to remote control your parent's linux system to guide them through some task, then VNC is the only option for you, because none of the others let you remote control an existing session. And if you just want to run a CLI command on your linux system, then SSH is the simplest method [1] You can tunnel X over SSH of course, if you care about security, but you still need an X server on the local machine to do this - you can't do it with just SSH.
I'd endorse nomachine www.nomachine.com It just seems to work well (for Kubuntu 7.10 and Dapper Drake) including access from Windows machine. I'd played around with VNC following the ubuntuforums but as Daniel says, performance does seem better using nomachine I haven't tried configuring nomachine for access over the internet whereas I have done that using VNC. VNC isn't encrypted unless you tunnel over ssh so there a little more work involved if encryption is important. But more importantly you don't want other people to be able to connect to your VNC server (if that the right term as X windows terminology is the other way around) I'd recommend nomachine if you want to access a linux box from a windows machine over a local network. Cheers On 30/01/2008, Daniel Lawson <daniel(a)meta.net.nz> wrote:
Zientek, Selene wrote:
Putty.exe vs. VNC Vs. X Windows???
Would anyone have any disadvantages or advantages of the subject above? Any thoughts would be very helpful?
They are all fairly different tools.
Putty is the name of a program used for SSH access - this will only give you command line (CLI) access in itself, so if you want to run a GUI app on linux you'll need something else.[1]. Putty isn't the only program you can use for this either.
VNC typically lets you connect to existing sessions. Some linux distros set this up so you can do remote-assistance type access, some set it up so you get a new login screen. VNC can be pretty slow, but you probably won't notice over a LAN.
X lets you start applications on the remote system and display them locally. This could be a single application, such as an xterm, or firefox, or it could be your entire window manager/desktop environment, such as GNOME or KDE, including the login screen. X is similar in concept to RDP, the MS Windows Remote Desktop Protocol, although it is very different in execution. However, you can do the same things with them - export your entire environment, or just export a single application.
There are also other technologies round, such as NoMachine NX, which is fundamentally similar in concept to X, but offers better performance. And there's tools like x2x, x2vnc, and synergy, which basically let you share a mouse and keyboard between multiple systems - eg, you can set it up so that if you scroll the mouse past the left hand side of the screen, it appears on the screen to your left, and you can control it there. This is useful if you have multiple computers with a screen each, but don't want to keep changing keyboard and mouse round.
The real question is, what do you want to do? If you have a windows machine at your desk and a linux machine elsewhere and you want to run a full GNOME environment, I'd really recommend using X (look for notes on setting up a windows X server and XDMCP on your linux system). If you want to remote control your parent's linux system to guide them through some task, then VNC is the only option for you, because none of the others let you remote control an existing session. And if you just want to run a CLI command on your linux system, then SSH is the simplest method
[1] You can tunnel X over SSH of course, if you care about security, but you still need an X server on the local machine to do this - you can't do it with just SSH. _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
participants (3)
-
Chris O'Halloran -
Daniel Lawson -
Zientek, Selene