Another thing to try is running the echoServer on TCP 443 (HTTPS)
rather than TCP 80 (HTTP). Since HTTPS traffic is typically SSL
encrypted, it's pointless for a firewall to "inspect" the traffic, as
it might
with normal HTTP.
cheers,
Scott
On Sep 25, 2006, at 6:26 PM, Barry E. Henley wrote:
> I'm running my echoServer for Windows v1.41 on port 80. I've had a
> very
> difficult time with some clients connecting to it. I've narrowed it
> down to
> clients running Netgear WGR614 v6 routers. I happen to own one of
> these as a
> spare and decided it was time to get to the bottom of the problem.
>
> I was able to duplicate the problem and have found the solution.
> The earlier
> firmware causes the connection problem. A connection can be
> resolved by
> temporarily turning OFF the SPI firewall under WAN setup. A permanent
> solution is to upgrade to the current firmware release.
>
> http://kbserver.netgear.com/products/wgr614v6.asp
>
> Barry in Acworth, GA USA
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users
