Which VNC Software Is Best?
Futurepower(R) writes "Which VNC software do you think is best, and why? There are several free programs, for example, TightVNC, RealVNC, UltraVNC, and TridiaVNC. Or, is it better to pay for VNC software, like Tridia VNC Pro or Radmin? Which is fastest, most secure, and the least hassle? Which has video resolution scaling of the remote desktop?"
The only VNC i have used is RealVNC, PCanywhere (Old) and Remote desktop for MS windows. I realize the best and most speedy one out of them all are actually Remote desktop that came with WindowsXP Pro and such.. I still use RealVNC for internet connection. The Java browser that does not requires software download are particularly useful. But perhaps it is time to check out the alternative... I didn't realize there are so many out there at all!
Yea, me too. It's not fantastic, being VNC after all. But it works pretty well, good video quality over a slower connection too. TightVNS is stable too.
- It's not the Macs I hate. It's Digg users. -
In a *nix-only environment, I prefer ssh with X forwarding.
I've heard there are products that serve X over low bandwidth.
You make the mistake of thinking you can educate the fundamental stupidity out of people. You can't.
This was cut and pasted from an email I sent to workmates a while back when I heard about NX initially. These days I prefer to use RealVNC (until I get around to buying a copy of NX) to connect to my XFCE session at home from the office.
Even on what you consider a fast connection (local ethernet) I prefer VNC over X11.
Man watching 6 MSCE's around a sun box, looks alot like the opening scene's of 2001:space odyssey...
Missing choice (you insensitive clods)! I only use microVNC! You know, for those times when you simply MUST remotely connect to the 8-bit microcontroller in your toaster when you're at work.
- "Hear that?! The percolations are imminent! Cease your ingress!"
If you're using VNC, you probably notice how slow it is. UltraVNC/TightVNC is a big improvement over regular VNC, as well as XWindows, but they're all dog slow.
NX (by NoMachine) and FreeNX (the GPL'ed edition) are REALLY fast, on the other hand. They are 100% encrypted through SSH and can tunnel to VNC, X, and RDP....
NX will currently only host from Unix/Linux. However, there are a bunch of clients.
I made an IMMEDIATE change to FreeNX/NX after using it only once. Now, I no longer use VNC for Linux....
FreeNX is for when it absolutely, positively, has to be double the speed. (-:
The NX protocol is essentially compressed and cached X; it talks to VNC, RDP and whetever else through its own proxy.
Mandrake 10.0 RPMs are here and here. The SRPMs will probably rebuild fine on 10.1 or 9.2 and are here and here.
Got time? Spend some of it coding or testing
I recently posted a list of the VNC's in debian, with a description of how each one serves a different purpose to LUGOD's vox-tech mailing list. The post is quoted here in full, so that you do not need to click the link, thereby slashdotting their server.
I was asked "Is there one implementation that's better than the others? Why did this piece of software fork so many times?"
And I answered as follows:
Because they're all different. Some for framebuffers, some serve differently, some compressed, some not. Read on, and I think you'll getthe idea.
(Search packages.debian.org for vnc, and you'll see all of these pop up.)
TightVNC uses JPEG or zlib to compress the data stream to optimize for lower bandwidth connections. It is under the GPL. Packages: tightvncserver, and xtightvncviewer
The default VNC viewer (packages vncserver and xvncviewer) are (c) 2002 RealVNC, and (C)1994-2000 AT&T. They are under the GPL. This seems to be
what you alien'ed.
x2vnc - use a vnc server as a second screen, so you can move the mouse between the local machine and a machine across the network that is running the vnc client.
directvnc - doesn't require x - uses libdirectfb-0.9-20. Depends on zlib and libjpeg, so it may work with tightvnc's protocol
svncviewer - depends on svgalib
x11vnc - the x11vnc server works the same way the Windows 2000 vnc server does - mirroring the physical screen over vnc
linuxvnc - "With linuxvnc you can export your currently running text sessions to any VNC client. So it can be useful, if you want to move to another computer without having to log out and if you've forgotten to attach a 'screen' session to it, or to help a distant colleague to solve a problem."
3dwm-vncclient - I think you get the picture
vnc-java - I think you know what this is. Why bother with it? Probably so you can serve yourself a vnc client over HTTP, probably.
tkvnc - a wrapper for xvncviewer