On Tuesday 21 February 2006 10:52, Scott C. Best wrote: > Hal: > > Heya. Have you tried EchoVNC? It has support for HTTP, > SOCKS, and NTLM proxies. For the first two, it relies on the > CONNECT method, which not all web-proxies support. But if your > target connection is listening to TCP 443 (ie, where HTTPS > traffic usually goes), the proxy will probably (as Phil pointed > out in his post) allow it. For EchoVNC, we run a demo echoServer > on both its normal port, and on TCP 443. > > Hope that helps!
>From what you say, I gather either the viewer or the server can not only create an outgoing connection, and not only on port 80, or port 443, but that it can make that connection use the HTTPS protocol, so a firewall would see it as an outgoing connection AND see the packets as HTTPS packets, so as long as it allowed outgoing HTTPS connections, it would let this out. Is that correct? And if I have no trouble with my firewall and can allow an incoming connection, do I need an echo server, or could I receive it on my end directly from the server? I figure I could always run an echo server on the same system I'm running echoVNC on, but it'd be great if I could skip that extra step. Also any idea how soon a Linux port might be available? Thanks! Hal _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
