TightVNC
TightVNC is a VNC distribution with many new features, improvements, and bugfixes over VNC. It is optimized for faster operation on slow network links such as modem connections, provides more configuration options in the server, features automatic SSH tunneling in the Unix vncviewer, and more. The modified servers and viewers are fully compatible with the original VNC software.
| Tags | Systems Administration Networking |
|---|---|
| Licenses | GPL |
| Operating Systems | POSIX Windows Windows |
| Implementation | C C++ Java |
Recent releases
- 11 Mar 2009 18:22
Changes: This release fixes various bugs that were reported for previous versions, and adds a number of minor improvements. The improved vncserver script is now able to read configuration files. Xvnc includes fixes for 64-bit Linux. There are a number of fixes and improvements in the Java viewer.
- 07 May 2007 21:49
Changes: This stable version includes support for the latest RFB protocol version 3.8, VNC4-compatible parsing of host:display strings, and a number of bugfixes and portability fixes. Also, there was many changes in the built-in Java viewer such as scaling, automatic encoding selection, support for ZRLE encoding, and a workaround for a Tab key problem.
- 16 Aug 2006 07:24
Changes: This version is expected to be the final release candidate for the upcoming stable release. The Unix version includes minor bugfixes and an improved built-in Java viewer with automatic encoding selection.
- 05 Apr 2006 03:13
No changes have been submitted for this release.
- 02 Jun 2004 03:39
Changes: A number of bugs were fixed in the Unix version, including problems with copying the clipboard to non-authenticated clients in Xvnc, delayed cursor shape updates in Xvnc, and crashing on switching between KDE virtual desktops in the viewer. A new -autopass option was implemented in the vncviewer.
- All comments
Recent commentsSetting Up ReverseVNC Connections
I've been getting quite a few hits on my family web page on how to compile two stand alone files using TightVNC to setup a reversevnc (reverse vnc) connection. I'm impressed with the continuing interest in the approach over the last year and a half. I've found that when the encoding protocol is set to "tight" with 8-bit color, the screen responsiveness is as good as UltraVNC and RealVNC even without DFMirage installed. I've also been able to use the files successfully with Vista Home Edition even though some websites suggest it shouldn't work. If you have any ideas for improving the reversevnc process you would like to share, freshmeat.net is the ideal location to post your suggestions to help others.
Check out how to compile the two stand alone files for automatically establishing reversevnc connections using TightVNC. http://brettschneider.us/ReverseVNC_Instructions/reversevnc.html
A superb project
I use TightVNC regularly to remote login to other hosts in the same network and also across cities. With DFMirage, it works unbelievably.
Now add to the fact this package is free...
I'm considering to contribute to the documentation in Indonesian. I've contacted Constantin to see if he is interested.
There are millions of users in third countries like mine who would like such a great free software.
So, thank you.
Re: More on Stand Alone Reverse VNC Connection File
Yes, I have run into this issue myself but don't have a solution. Since I'm controlling the remote computer, I just close out the application from the tool bar (bottom right) myself which immediately breaks the connection. FYI, I've posted a set of highly detailed and highly simplified instructions on how to create the reversevnc files on my family homepage.
http://brettschneider.us/ReverseVNC_Instructions/reversevnc.html
Re: More on Stand Alone Reverse VNC Connection File
>
> % Oops, another typo. It should be
> % VNCviewer.exe not VNCviewer.dll
> % Also, I've discovered that to make
> the
> % final exe run under Vista (no problem
> % under XP), you need to create two
> .reg
> % files out of two WinVNC folders from
> the
> % registry, one under HKEY_CURRENT_USER
> % and the second one under
> % HKEY_LOCAL_MACHINE. There is a third
> one
> % under HKEY_USERS that can be ignored.
> % Name the two reg files: WinVNC.reg
> and
> % WinVNC2.reg
> %
> % Modify the bat file contents to read:
> %
> % %myfiles%\regedit.exe /s winvnc.reg
> % ping -n 1 127.0.0.1
> % %myfiles%\regedit.exe /s winvnc2.reg
> % ping -n 1 127.0.0.1
> % start %myfiles%\winVnc.exe
> % ping -n 2 127.0.0.1
> % %myfiles%\WinVNC.exe -connect
> % 70.112.yyy.xxx::5500
> %
> % Follow previous instructions.
> %
> % Good Luck
>
>
>
>
> TNX FOR THIS MAN!
> in just have to give you some feedback.
> this actually does work. just need to
> test it on vista to.
> it's like you said - you usually spend
> more time on telling a customer on how
> to connect you with "add new client"
> than the actual problem is.
>
> thanks again! and keep up the good work.
>
>
just another question ...
any idea how to solve this:
when the customer runs this bundled exe, it brings him up tightvnc server and connects to vnc client on my computer. when connection is closed, the server is still running at my customers computer. if my client clicks the exe (the one we speak of here) again it crashes and shows an error. customer must close the server and click the exe one more time to load the server again and connect.
is there an elegant way to check if the server is already running before it connects to client? it would be nice that the client does not see any error messages. it scares them. :)
Re: More on Stand Alone Reverse VNC Connection File
> Oops, another typo. It should be
> VNCviewer.exe not VNCviewer.dll
> Also, I've discovered that to make the
> final exe run under Vista (no problem
> under XP), you need to create two .reg
> files out of two WinVNC folders from the
> registry, one under HKEY_CURRENT_USER
> and the second one under
> HKEY_LOCAL_MACHINE. There is a third one
> under HKEY_USERS that can be ignored.
> Name the two reg files: WinVNC.reg and
> WinVNC2.reg
>
> Modify the bat file contents to read:
>
> %myfiles%\regedit.exe /s winvnc.reg
> ping -n 1 127.0.0.1
> %myfiles%\regedit.exe /s winvnc2.reg
> ping -n 1 127.0.0.1
> start %myfiles%\winVnc.exe
> ping -n 2 127.0.0.1
> %myfiles%\WinVNC.exe -connect
> 70.112.yyy.xxx::5500
>
> Follow previous instructions.
>
> Good Luck
TNX FOR THIS MAN!
in just have to give you some feedback. this actually does work. just need to test it on vista to.
it's like you said - you usually spend more time on telling a customer on how to connect you with "add new client" than the actual problem is.
thanks again! and keep up the good work.