Diego:
That's a tricky one...EchoVNC acts very much like an SSH-client: when
it starts up, it tries to logon to the echoServer it's been told about.
If those
logins fail (eg, due to no network connection), it won't try to
auto-reconnect
to them.
In the application you use to manually connect to the Internet, is
there
the ability to have it auto-start an application after it completes?
-Scott
PS: The BlacklistTimeout registry value isn't set by default in the
registry, so
you won't find it with a search. You'll have to add it manually in:
HKEY_LOCAL_MACHINE\Software\RealVNC\WinVNC4
On Jul 20, 2005, at 6:10 PM, Diego Ledesma wrote:
Hi again.
I checked the echoserver DNS and it's demo.echovnc.com (sorry for
that) and i'm connected to it.
I also tryed to find the BlacklistTimeout registry value but i
couldn't find it (i did a full registry search).
One more thing. EchoVNC starts at Windows startup and if at this
point i'm not on-line it won't be connected to the EchoServer (that's
obvious). Then i manually connect to the Internet but EchoVNC doesn't
try to connect to the echoserver, i have to do this manually.
That's not good for me because the computers i want to manage don't
go on-line automatically.
Thanks.
Diego.
2005/7/20, Scott C. Best <[EMAIL PROTECTED]>:
Heya. First off, just to be sure, the demo echoserver is at
"demo.echovnc.com", with a password "demo2005". Just checking to make
sure you're connected to the right place. :)
Also, there's a minor incompatibility between EchoVNC and
RealVNC 4.1.1 that will cause connections to occasionally fail.
Problem is that when EchoVNC periodically checks to see if the RealVNC
server is running, the server can come to believe that EchoVNC is a
"denial of service" attack, and so it refuses future connections from
EchoVNC for a few minutes -- and the more repeated failures it
detects,
the longer RealVNC will refuse connections from you. The best thing to
do is to simply leave it alone for ~2 minutes, and try again.
In the 1.34 release of EchoVNC, we'll fix this
incompatibility.
In the meantime, you can workaround this wait time by setting
RealVNC's
"BlacklistTimeout" registry value to "0".
cheers,
Scott
On Wed, 20 Jul 2005, Diego Ledesma wrote:
> I'm new to VNC and EchoVNC, so when an error window comes up i
don't know
> what's not working.
> I installed RealVNC 4.1.1 Free Edition and also EchoVNC 1.33 here
at home. I
> configured RealVNC and EchoVNC. Then i installed the same two
programs in
> two computers i want to remotely manage, one of them uses internet
sharing
> connection to be on-line, the other one is the one that has the
router - DSL
> modem.
> I installed EchoVNC and RealVNC in the one that has the
router-modem, then
> tryed to connect from home and worked fine.
> Then i installed both programs in the other computer and also
worked fine.
> The problem came when i tryed to connect to the frist computer
again. A
> window error saying "unable to connect to host: Connection refused
(10061)"
> comes up.
> I checked if the echoserver
(demo.echoserver.com<http://demo.echoserver.com/>)
> was connected and it was.
> I re-connected and another error message came up, this one said
something
> like "couldn't connect to the echoserver
> demo.server.com< http://demo.server.com/>,
> check your information and password".
>
>
> Thanks in advance.
>
> Diego.
>
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users
