From: Scott Best [mailto:[EMAIL PROTECTED]
Sent: Mon 4/25/2005 7:35 PM
To: Lewis, James
Cc: [email protected]
Subject: Re: [Echovnc-users] Connection closed unexpectedly
James:
Heya.
Which version of EchoVNC? The 1.0 release didn't work great
with RealVNC 4.x
servers due to their new security enhancements between
failed connection
attempts -- it perceived EchoVNC's periodic checking
of
the VNC Server as
a failed authentication attempt. We tried to address
that
fix in the 1.1
release.
But ... you're seeing
this with TightVNC servers as well?
-Scott
On Apr 25, 2005, at
4:07 PM, Lewis, James wrote:
> Getting 'connection closed
unexpectedly'. Sorry if this is covered
> elsewhere, but I couldn't find
it.
>
> Both ends XP Pro, SP2, echovnc installed and
running and showing
> connected to demo.echovnc.com .
>
> From either side a connection attempt to the username of the
other
> user successfully finds the partner, then seems to start
connecting,
> then does nothing for a second or two, then reports
Connection closed
> unexpectedly (or something similar).
>
> Using RealVNC one end, tightVNC the other, with default viewer at
both
> ends.
>
> Log looks like this:
>
>
> Connect2Partner begins
> Use the proxy
65.19.178.123:1328
> =>lpfnEstablishNewDataChannel
>
<=lpfnEstablishNewDataChannel returned 3604
> StartVNCViewer:
127.0.0.1:3604
> ConnectionThread ends
>
>
ConnectionThread begins
> CONNECT_VIA_ECHOSERVER
> Connect2Partner
begins
> Use the proxy 65.19.178.123:1328
>
=>lpfnEstablishNewDataChannel
> <=lpfnEstablishNewDataChannel
returned 3628
> StartVNCViewer: 127.0.0.1:3628
> ConnectionThread
ends
>
>
> Thanks for any
help!
