Franklin:
Heya. You're right: EchoVNC won't "find" your RealVNC server if it's
not running in the standard 5900-5909 range. There's no easy way to
change that, without changing the source.
As for your "EchoWinVNC" comment, I'm not sure what you mean.
EchoWinVNC uses dynamic ports and only makes outgoing connections,
so it needs no port-forwarding. As for the echoServer, it has a port
setting region on the main page. Can you clarify your concern here?
thanks,
Scott
PS: The problem with UDP punch-thru is the reliability. At best, it's a
90-percent solution. So I think echoWare/echoServer will always have
to at least "fall back" to TCP relaying. Still, we're looking into
extending
the echoWare protocol to accomplish this..
I finally took some time this morning to try out EchoVNC and ran into
the following problems:
1) EchoVNC client is not finding my RealVNC server. I guess this is
because I run it on a non-standard port (>40,000). Is there a way to
set the VNC port in EC?
2) EchoWinVNC does not have a way to specify a non-standard port. I
had to set my router to forward TCP from the standard port on the
internet to the non-standard port on my ES. Is there a way to set the
EchoVNC port on EW?
Thanks!
PS What are the plans/progress for UDP punch through? This is a
feature that interests me just to hopefully reduce/eliminate the
packet relaying the server must do. Thanks!
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users
