Issue with connecting to Vnc via router.

[Scott C. Best]

Wez:

  	I'm sorry to disagree, but my experience has been that most
commercial NAT'ing routers (eg, LinkSys, Netgear) are unable
to route traffic in a "loop" manner as described. Perhaps the very
latest products allow this, or perhaps I could simply be wrong:
if other users on this list have routers which allow this, please
feel free to let me know and I'll update the FAQ-O-Matic entries
about this topic accordingly.

  	I also agree that the configuration interface should only
appear on the internal interface, but most of the commercial routers
I've worked with have a radio-button option to enable the external
side as well.

cheers,
Scott


> On Dec 1, 2004, at 2:49 AM, James Weatherall wrote:
> 
>> Scott,
>> 
>> Unless there is something wrong with LAN's access to the Internet, your
>> statement regarding access to servers is incorrect.  The router should
>> respond on its external (WAN/Internet) IP address even within the LAN.
>> 
>> Your statement regarding "router logon box"s is also incorrect, I think.
>> Routers should only serve their configuration interface (assuming it is HTTP
>> based), on their LAN address, and not via their WAN address.
>> 
>> So, to clarify:
>> 
>> - XXXX.myserver.org should work from both the Internet and the LAN.
>> - You should only see the router's configuration pages if you browse to its
>> LAN address (probably 192.168.0.1 or similar).
>> 
>> It sounds as though the routers discussed here are broken in that they
>> regard traffic for their WAN address as equivalent to traffic for their LAN
>> address, when received on the LAN interface.
>> 
>> Regards,
>> 
>> Wez @ RealVNC Ltd.
<snip>