Trouble connecting

[Scott C. Best]

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