Rich:
Hello! If you're connecting to your echoServer from a PC on the same
network as the echoServer, you'll need to login to it using the LAN IP
address,
not the external IP address.
To connect to it from the external side, you'll have to open a port in
your Linksys box. Details for that at "http://www.portforward.com";. Just
choose your model, then choose "echoserver" as the service.
Also, lastly, many ISP block connects to ports other than the "well
known" ones. Having the echoServer listen to its own port (TCP 1328)
as well as TCP 443 is probably best.
cheers,
Scott
On Sep 14, 2008, at 1:32 PM, Rich Costabile wrote:
> I seemed to have loaded ES correctly on my XP system but it doesn't
> show up when running the test to connect to it from the network. My
> configuration is 2 xp machines on a linksys hub and a wireless
> laptop connected to the hub. The hub is connected to Comcast network
> cable.
>
> Please help. I think the hub may be blocking the connections. This
> is the message that I receive
>
>
> Error: I could not see your service on 76.101.3.222 on port (1328)
> Reason: Connection timed out
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Echovnc-users mailing list
Echovnc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/echovnc-users
