Fred:
Hello! I presume you're using 1.40 version of the echoServer. Once
it is up and running, please note the "Check Server" button. Click that,
and a web-page will open to a site that will try to "see" your
echoServer
from the outside of your LAN. If the scan fails, then you most likely
still
have a firewall/router blocking connections to your echoServer.
So you may still have one port-forwarding adjustment you need to
make to your firewall/router. That can be tricky, but there's some
detailed
info on how to do it here: "http://www.portforward.com";. When you make
the adjustment correctly, the "Check Server" scan will report success.
The good news is that once you've made this adjustment, all of
the subsequent VNC connections that you make via the echoServer
won't need any adjustments at all.
hope that helps,
Scott
On Jul 2, 2005, at 3:50 AM, Marcel wrote:
Hi,
I installed EchoServer on my laptop. It's up and running.
Then I try to add the server to Echo-vnc /tab/Echoserver with the
following
settings:
192.168.1.104:1328. So far so good.
Now I want a remote computer to access the EchoServer. The WAN IP
adress on
which the server is running is 82.75.69.117 but when I use that, there
is no
connection. The hostname of my pc is cc522600-a and ipconfig sais:
hnglo1.ov.home.nl
So I tried cc522600-a.hnglo1.ov.home.nl but that doesn't word either.
What settings should I use?
Best Regards,
Fred Zoer
-------------------------------------------------------
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_id=7477&alloc_id=16492&op=click
_______________________________________________
Echovnc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/echovnc-users
