Fred:
Heya. I presume you're running version 1.40 for Windows?
If so...after you start your echoServer, the "Check Server" button
will activate. Click that button, and it will open a web browser
that connects you to a web-page that "port scans" your WAN IP
to try and find your server running on port #### (default 1328).
If you've correctly port-forwarded this port across your router
to your EchoServer PC, this scan will indicate success. If it
cannot detect your server, there's still something "blocking"
the connection (eg, a "Personal Firewall" on the EchoServer PC).
The good news is this: once you *can* connect to your
echoServer from outside of your LAN, you won't need to touch
port-forwarding again for any of the VNC connections. Trick is,
you still have to solve it once...
hope that helps.
Scott
On Wed, 29 Jun 2005, Karin en Fred Zoer wrote:
Hi,
I am havingtrouble to make connection to the EchoServer.
The EchoServer is installed on my home laptop, that's behind a router.
Ipconfig sais my hostname is cc522600-a and connection-specific DNS Suffix is
hnglo1.ov.home.nl
The local Ip adress of my laptop is 192.168.1.104
On my laptop I can connect to the EchoServer through 192.168.1.104. From a
remote computer I tried toconnect to the EchoServer on many different ways:
cc522600-a.hnglo1.ov.home.nl
192.168.1.104
82.75.69.117 (my wan ip)
Nothing seems to work. And before I buy the software I must know if it works.
Please can you help me?
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
