Install gave me the VNC warning on a PC running VNC 4.1.1 !! SO
loopback not on the VNC dialog.:-{
Hmm, I guess what it *really* checked was the registry ...and I still had
some debris there from V3 [confirmed]
I just let the change go ahead and will delete the registry
HKEY_LOCAL_MACHINE\Software\ORL\WinVNC3\
entry unless you tell me otherwise e.g. if VNC 4 still uses this but it's
not in its GUI.
If you have one of the older "version 3" flavors of VNC installed, you may
need
to add the "AllowLoopback" setting to your VNC Server in order for EchoVNC
to work with it. EchoVNC's Startup Wizard will automatically make this
adjustment, but are two ways to enable this setting manually as well:
^ there
~~~~~~~~~~~~~~~~~
GUI connect dialog
{I just did a simple VNC connection here at home as I can't get through to
my echoPC at work via an echoserver...}
heading shows Partner or ip/DNS and then has [echo server] and [direct
connection] buttons.
I'm not 100% sure what this dialog means, but I take it to mean
if pressing [echo server} then text box contains PartnerID
if pressing [direct conn} then text box contains ip/DNS
{having a partnerID matching an in-scope DNS name makes my head ache and
you'll need to elaborate that scenario for me in your reply}
If my understanding of it being a binary choice, then maybe a radio-button
to select between [echo server] and [direct connection] would then be
followed by a Text box with a description corresponding to the choice (or
maybe switch greyed out text as radio-button toggles)
Then there would be only two [buttons] viz. [Connect] and [Cancel]. This
would make the GUI easier for simpletons like me to comprehend .
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Further...
I note in the on-line help user guide step 3
<<Choose whatever "Userid" you prefer, just not the same name as one of your
VNC targets">>
Why "not" ? ..is that only a problem if the connect dialog is as current
and the wrong button is pressed or can some other name clash occur ?
I just experimented with a partner PC on my home lan with DNS name the same
as partner and the direct connection worked but the via echoserver found
and connected but then said
"VNC Viewer : Question
? The connection closed unexpectedly
Do you wish to reconnect to 127.0.0.1:2147?" {and :2154 on the
attempt logged below}
When I tried this a few months back it worked just fine so maybe I've
smashed some crucial configuration details or upgraded VNC perhaps ?
note that one log uses local date format and the other uses U.S. format for
this infamous day>>>>
11/09/2005 04:01:08.161 echowarelog is ON
11/09/2005 04:01:15.271
ConnectionThread begins
11/09/2005 04:01:15.271 CONNECT_VIA_ECHOSERVER
11/09/2005 04:01:15.281 Connect2Partner begins
11/09/2005 04:01:15.281 Use the proxy 65.19.178.123:1328
11/09/2005 04:01:15.281 =>lpfnEstablishNewDataChannel
11/09/2005 04:01:16.423 <=lpfnEstablishNewDataChannel returned 2153
11/09/2005 04:01:17.935 StartVNCViewer: 127.0.0.1:2153
11/09/2005 04:01:17.975 ConnectionThread ends
######
[09/11/05-04:01:15] ENDC Dll : Sending MSG_PROXY_FIND_PARTNER message to
proxy
[09/11/05-04:01:15] AC Dll : Received Bytes on Authentication Socket Socket
: 36
[09/11/05-04:01:15] Dll : Received Message - MSG_PROXY_PARTNERFOUND.
[09/11/05-04:01:15] ENDC Dll : 2k3home Partner was found with Proxy
65.19.178.123:1328
[09/11/05-04:01:15] ENDC Dll : Partner Found for Establishing new Data
Channel..
[09/11/05-04:01:15]
[09/11/05-04:01:15] ENDC Dll : Sent MSG_CONNECT_TO_PEER message to
echoserver
[09/11/05-04:01:15] AC Dll : Received Bytes on Authentication Socket Socket
: 39
[09/11/05-04:01:15] ENDC Dll : Received message - MSG_CHANNEL_CODE.
[09/11/05-04:01:16] AC Dll : Received Bytes on Authentication Socket Socket
: 359
[09/11/05-04:01:16] ENDC Dll : Received message - MSG_PEER_KEY.
[09/11/05-04:01:16] EncDec val for this proxy is : 0
[09/11/05-04:01:16] AC Dll : Connection to echoServer via Direct
[09/11/05-04:01:16] ENDC Dll : Sending MSG_DATA_CHANNEL_CONNECT GetLastError
returned : 0
[09/11/05-04:01:16] ENDC Dll : Created Listening Socket on Port : 0
[09/11/05-04:01:16] Added Socket : 812 to the connection list
[09/11/05-04:01:16] AC DLL : Get the client public key....
[09/11/05-04:01:16] AC DLL : Session key for data channel generated....
[09/11/05-04:01:16] Session Key : 000
[09/11/05-04:01:16] Encryption/Decryption Option : 0
[09/11/05-04:01:16] Added Socket : 828 to the connection list
[09/11/05-04:01:16] ENDC Dll : Establish Data Channel Event Set...
[09/11/05-04:01:16] ENDC Dll : New listener socket port returned by the Dll
: 2153
[09/11/05-04:01:16] ENDC Dll : Waiting for initiator to connect to port :
2153
[09/11/05-04:01:18] ENDC Dll : Accepting Client socket for Data Proxying
:776
[09/11/05-04:01:18] New socket : 828 added to complete socket pair : 776 in
list
[09/11/05-04:01:18] ENDC Dll : Accepted Client socket for Data Proxying :
127.0.0.1:2154
[09/11/05-04:01:20] Shutting down and closing socket : 812
[09/11/05-04:01:20] Removing Listener Socket : 812
[09/11/05-04:01:20] deleting conn object
[09/11/05-04:02:05] Dll : GetlastError : 0
[09/11/05-04:02:05] Dll : 65.19.178.123:1328 Proxy server disconnected with
SendRemoteMessage ret val : 0
[09/11/05-04:02:05] Shutting down and closing socket : 524
[09/11/05-04:02:05] Done removing socket
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users
