|
Scott, It looks like it was a Win98 problem? I tried again and got things to work :-) But, the remote window disappeared shortly after it got started? John [EMAIL PROTECTED] wrote: Send Echovnc-users mailing list submissions to [email protected]To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/echovnc-users or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than "Re: Contents of Echovnc-users digest..." Today's Topics: 1. Re: Problem using EchoVNC with a my own EchoServer? (Scott Best) --__--__-- Message: 1 Cc: [email protected] From: Scott Best <[EMAIL PROTECTED]> Subject: Re: [Echovnc-users] Problem using EchoVNC with a my own EchoServer? Date: Mon, 13 Jun 2005 22:14:46 -0700 To: [EMAIL PROTECTED] John: Heya. When you substitute your echoSever (ie, one of your LAN PC's at 192.168.2.x), did you connect your EchoVNC clients to it using that IP address? Or did you connect to it using the FQDN "johnhenrymiller.com"? Depending on your router...the echoVNC clients may not be able to connect to an "external address" that's actually port-forwarded to a local machine. Many routers simply aren't that smart. Try using the local LAN address instead, see if that helps... -Scott On Jun 13, 2005, at 5:09 PM, John H Miller wrote: |
