Comments for TightVNC

Setting 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 &quot;tight&quot; 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

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

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. :)

> 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.

Unable to connect to server
I recently replaced a Windows 2000 PC (at a remote location) with another because of hardware problems. I was able to control the &quot;old&quot; W2K PC using the installed TightVNC 1.2.9 running as a service. I'm not able to directly control the &quot;new&quot; PC using TightVNC, the connection times out. Nothing has changed on the firewall so it's not a firewall issue.

Nor is it a TightVNC server issue since I'm able to remotely control the PC through a TightVNC viewer session established on another PC in the remote workgroup. This is a horrible way of doing the job, the screen refresh is slow and erratic.

Is there an obvious answer to this? Or is there some diagnostic information that I can access which will help in troubleshooting? Deinstalling and reinstalling TightVNC doesn't help.

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

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

Again, my reason for making a single executable was to simplify the reverse vnc process, which I used this very evening to help a relative install a webcam. The appearance of the application icon in the taskbar and likelihood that the firewall requesting permission to allow a connection should be enough alert to prevent abuse. But, with some of the tools available and some trickery, anything is possible I suppose.