Trouble connecting Solved

[wretchedwight@sunvalley.net]

I just wanted to let you all know that I have solved my issue. I had
everything relating to RealVNC configured properly, but had screwed  up at
the dynamic update client level. You know it just really takes us who are
unfamiliar with this kind of thing a while to figure it out. You guys
should have patience with us, sometimes we are reading the docs, and yes
they are in plain English, but we still stumble with it. Thanks to
everyone who took the time to help. -Jeff


> Jeff:
>
>  	Heya. When you get the timed out message...are you testing
> it from "inside" the NAT'd LAN, or from the "outside"? It's not
> obvious, but it won't work if you're testing from the inside; if
> gotomyvnc shows both displays are responding, that's as good as
> internal-testing can get.
>
>  	Hope that helps! Please let me know if you have any luck
> with EchoVNC. It's Windows-only right now, and the server itself
> is "shareware", but it all works as advertised with any "flavor"
> of VNC server or viewer.
>
> -Scott
>
> On Fri, 1 Apr 2005 wretchedwight "at" sunvalley.net wrote:
>
>> Hi, thank you for you help. I adjusted this yesterday and now
>> gotomyvnc shows that both displays are accepting connections.
>> Nevertheless, I still can not connect remotely from outside the router
>> level. I know I must be missing something easy but... Still getting
>> the timed out message. I may have to try the echovnc idea. It just
>> bugs me that I can't figure it out. Do you know if I need to turn off
>> NAT in the router configuration? -Jeff
>>
>>> Jeff:
>>>
>>>  	Heya. I think the problem is that the server on your second
>>> machine (.251) is still listening to "display 0" (ie, TCP 5900)
>>> rather than "display 1" (TCP 5901). You can either change the VNC
>>> Server to listen to the right port, or change the port-forwarding so
>>> that it maps 5901 (external) to 192.168.0.251:5900 (internal).
>>>
>>>  	A slightly more "scalable" way to do it is to install an
>>> echoServer on one of your internal PC's, and setup port-forwarding
>>> for just that one PC. Then from each of your RealVNC servers and
>>> viewers, connect to that echoServer with the echoVNC utility. The
>>> echoServer then acts as a "relay" for all of the VNC connections. You
>>> can find more info at "www.echovnc.com".
>>>
>>>  	Hope that helps!
>>>
>>> -Scott
>>>
>>>
>>>> Hi all. I am trying to get my VNC up and running. I tried in the
>>>> past and received some good advice but in the final analysis failed
>>>> to get something properly configured.
>>>>
>>>> I am using an Actiontec modem
>>>> (http://www.qwest.com/dslhelp/modems/gt701/index.html#configuration)
>>>> on both ends. I have set up static IP addresses on all machines and
>>>> have port 5900 forwarded like this,
>>>>
>>>> The setup configuration screen asks for a port rang so I put:
>>>> 5900-5900 TCP 192.168.0.250 	for first machine
>>>> 5901-5901 TCP 192.168.0.251	for second machine
>>>>
>>>> VNC works at the subnet level if that is the right way to say it.
>>>> When I go to gotomyvnc.com it says:
>>>> xxx.xxx.x.xxx is accepting connections on Display 0 (TCP port 5900).
>>>> xxx.xxx.x.xxx is not responding on Display 1.
>>>>
>>>> I am using no-ip for my dynamic router address. xxxxxx.no-ip.info
>>>> The error message I get when I try to connect from the office is:
>>>> Unable to connect to host: connection timed out (10060)
>>>> Any insight would be greatly appreciated. -Jeff