Mark:
Heya. Some replies inline:
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 ...
Yes: if EchoVNC sees that there is "V3 debris" in the registry, it will
presume that you still use a VNC flavor that requires the AllowLoopback
connection.
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
That's correct.
{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}
As you said: if you click "Connect via EchoServer", it will presume the
connection data is a PartnerID. If you click "Connect Directly", it
will presume
the connection data is IP/DNS.
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 .
In the future, we'll actually have a "point and click" interface, so
it'll
be much easier to utilize that radio buttons.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~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 ?
When you ask the echoServer to begin relaying a VNC connection, it
just needs to know with whom to activate the connection. So if you're
logged in as "MarkPC" and someone else is logged in to the same
connection group as "MarkPC", if I tried to connect to "MarkPC", the
echoServer wouldn't know which one I meant.
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 ?
Using the above example, if you were trying t connect *to*
"MarkPC" while at the same time connected from "MarkPC", it's
possible that the echoServer will actually attempt to connect you
to yourself.
Also, regardless of this "username clash", if you simply
enter the wrong password, the VNC server may close the connection
before the VNC Viewer gets the "bad password" message. The only
thing EchoVNC can then report is "the connection closed unexpectedly".
Hope that helps!
-Scott
-------------------------------------------------------
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
