Re: No-IP and Real VNC on multiple PC's‏

Dale Eshelman <[email protected]>
Newsgroups gmane.network.vnc.user,gmane.network.vnc.realvnc.general
Message-ID <[email protected]>
I am familiar with the link. I just thought there was something  
special you were addressing I did not know. I do not know a router  
that does not have port forwarding.
I just thought the term "NAT" referenced something special regarding  
routers. So I guess "Net Address Translation" is the same as port  
forwarding.

On Sep 26, 2009, at 05:09 AM, Philip Herlihy wrote:

> You may find this helpful:
>
> http://portforward.com/
>
> Philip Herlihy	
>
>
> -----Original Message-----
> From: [email protected] [mailto:vnc-list- 
> [email protected]] On
> Behalf Of Dale Eshelman
> Sent: 26 September 2009 02:55
> To: Christopher Woods
> Cc: 'Bob Grabbe'; [email protected]
> Subject: Re: No-IP and Real VNC on multiple PC's‏
>
> Can you provide an example of of the setting and location of setting
> on the router that need to take place for NAT? What must a router have
> in the settings to be a NAT router?
> Thanks
>
> On Sep 25, 2009, at 12:28 PM, Christopher Woods wrote:
>
>>
>>> I've done this before, although only with two pc's behind the
>>> same router.
>>> For example, the router is set up to forward port 5900 to
>>> pc1, with the ip of 192.168.1.50 and port 5901 to pc 2 with
>>> the ip of 192.168.1.51.
>>> PC1 is set in vnc to listen on port 5900 and pc2 is set to
>>> listen on port 5901. You set this on the connections tab of
>>> the options for the vnc server on each pc.
>>> If I want to connect to pc1, I run the vnc client ( from work
>>> ) to the No-ip address:5900, if I want to connect to pc2,
>>> it's the No-ip address:5901.
>>
>> With a good NATting router, having to change the listen ports on
>> each PC
>> *shouldn't* be necessary, but it can make things simpler. (however
>> if you're
>> connecting from those machines via a LAN it adds the requirement to
>> specify
>> the port as well, which I dislike...)
>>
>> If the 2Wire can only directly map incoming traffic to the
>> equivalent port
>> on the internal machine, then Roberto will have to do that. As long
>> as his
>> router supports restricted or full cone NAT and allows for differing
>> local
>> and remote port assignments, he should only have to make his changes
>> on the
>> router (all the LAN PCs will quite happily work with the default
>> settings).
>>
>>
>> _______________________________________________
>> VNC-List mailing list
>> [email protected]
>> To remove yourself from the list visit:
>> http://www.realvnc.com/mailman/listinfo/vnc-list
>
>
> Dale Eshelman
> [email protected]
>
> ShopToEarn (Dist ID 105985)
>  http://www.ShopToEarn.net/DaleEshelman
>
> MonaVie (Distr ID 1316953)
> http://www.monavie.com/Web/US/en/product_overview.dhtml
>
> The closer I get to the pain of glass in Windoz, the farther I can see
> and I see a Mac on the horizon.
>
> _______________________________________________
> 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


Dale Eshelman
[email protected]

ShopToEarn (Dist ID 105985)
  http://www.ShopToEarn.net/DaleEshelman

MonaVie (Distr ID 1316953)
http://www.monavie.com/Web/US/en/product_overview.dhtml

The closer I get to the pain of glass in Windoz, the farther I can see  
and I see a Mac on the horizon.

_______________________________________________
VNC-List mailing list
[email protected]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.