=?windows-1256?Q?RE:_No-IP_?= =?windows-1256?Q?and_Real_V?= =?windows-1256?Q?NC_on_mult?= =?windows-1256?Q?iple_PC's=FE?=

Hello:

 

I think I'm missing something on my 2Wire 2701HG-T router configuration or somewhere else.

 

I can only connect to the PC (the main one) that has the No-IP client installed.
 
I added an exception on Windows XP firewall on each of the 7 PC's
 
So for the main PC I added the exception port TCP 5900
So for PC1 I added the exception port TCP 5901
So for PC2 I added the exception port TCP 5902
So for PC3 I added the exception port TCP 5903
So for PC4 I added the exception port TCP 5904
So for PC5 I added the exception port TCP 5905
So for PC6 I added the exception port TCP 5906
 
I'm entering on the VNC Viewer papeleria.no-ip.org:5901 to try to connect to PC1 but I can't.
 
How am I supposed to configure the router?
 
What I did was to forward ports 5900 through 5901 to the IP address if the main PC (192.168.1.71) where the No-IP client is installed.
 
Am I missing something?
 
Thanks
 
> From: [email protected]
> To: [email protected]; [email protected]
> Subject: RE: No-IP and Real VNC on multiple PC's‏
> Date: Sun, 27 Sep 2009 14:16:34 +0100
> CC: [email protected]
> 
> > My understanding of NAT is that a router must be able to 
> > associate multiple connections (possibly connectionless UDP 
> > conversations) between its LAN clients and external stations 
> > which can see only the router as a single entity. So, if a 
> > UDP datagram arrives from a station on the WAN the router 
> > must be able to “remember” which of its clients it should be sent to.
> > 
> > 
> > 
> > Port forwarding is a fixed configuration, where a connection 
> > on a particular port (e.g. 5900 or 5500) is always routed to 
> > a particular client. The most helpful routers allow the port 
> > to be translated, so you can connect to the router on port 
> > 8903 or port 8904 and the router will send the connection to 
> > 10.0.0.3 or 10.0.0.4 respectively, while translating the port 
> > on the LAN side to 5900.
> 
> 
> Entirely accurate; apologies for any confusion from my earlier response. I
> was not attempting to conflate static port forwarding with NAT (I was just
> indicating that if his router can happily handle NAT, it should be able to
> support multiple port forwards ;)
> 
> The NAT capabilities might come in to play if the server is set to connect
> to an external listening client...
> 
> 
> _______________________________________________
> VNC-List mailing list
> [email protected]
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list
 		 	   		  
_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list