Re: TightVNC vs TeamViewer

[Scott C. B. <sb...@ka...>]

John:

 	Hello! Yes, the echoServer itself is a "try before buy" commercial
binary. It's pretty darn functional in its "unregistered" state, though
actually registering it helps us keep the lights on. :)

-Scott

On Sun, 20 Dec 2009, john s wolter wrote:

> Scott,
>
> Thank you for responding, I'll take a look at it to see how it works.  The
> only concern is the echoServer not being GPL'd if I understand what you had
> to say about it.
>
> Cheers.
>
> On Sun, Dec 20, 2009 at 1:27 PM, Scott C. Best <sb...@ka...> wrote:
>
>> John:
>>
>>        Hello! I built a VNC-based system similar to TeamViewer, that
>> can be configured to work directly with TightVNC. It's called EchoVNC,
>> and works like this:
>>
>> 1. Install EchoVNC on your TightVNC Server. EchoVNC by default comes
>>   with its own VNC service (we built our from the UltraVNC distro),
>>   but one of the configuration options lets you work with an already
>>   running VNC service. We also have a "zero config" version of the
>>   VNC server called InstantVNC, in case you just want to email
>>   something to a remote user that's not running VNC yet.
>>
>> 2. Install EchoVNC on your TightVNC Viewer. Again, EchoVNC has it's
>>   own VNC Viewer application, but it can be configured to work with
>>   another platform's viewer.
>>
>> 3. On both sides of the connection, login to the same echoServer.
>>   Think of that application as a "relay server" similar to what
>>   the TeamViewer service provides. In this setup, the echoServer is
>>   the only piece that requires firewall or NAT configuration. A
>>   static IP address for the echoServer is useful, but a dynDNS
>>   addrees also works. Once both sides (Viewer and Server) can
>>   connect and login, they can connect to each other.
>>
>>        Once that's all setup, start the EchoVNC Viewer, and it will
>> display a "point and click" list of remote clients you can kick off
>> a TightVNC Viewer session with. Also, the "tunnel" created between
>> the Viewer and Server and the echoServer during the VNC session is
>> SSL-secured.
>>
>>        Everything except the the echoServer (a shareware download
>> available for Linux and Windows) is VNC-based, so all of those pieces
>> are GPL'd open-source. More details here:
>>
>> http://www.echogent.com/download_echovnc.htm
>>
>>        Hope this helps, and I welcome any suggestions for improvement.
>>
>> cheers,
>> Scott
<snip>