Re: network problem: configuration/DNS? cannot access internal machine using our external IP

[Gary Turner <kk5st@sbcglobal.net>]

Jerome Lacoste (Frisurf) wrote:

>On Wed, 2003-02-12 at 20:20, Gary Turner wrote:
>> Jerome Lacoste (Frisurf) wrote:
>> 
>> >Summary: If I try to connect to an internal server given its dyndns.org
>> >hostname, it works from the outside world, but fails if I try from
>> >within our intranet.
[...]
>> >
>> Your gateway/router is working as designed.  The internal (LAN) and
>> external (WAN/Internet) are kept separated.  This means that no WAN IP
>> can try to connect directly with an internal address.  Nor is it allowed
>> to use a LAN IP from outside.  When you try to connect to your public
>> address from within the LAN, the name resolves to your own address.  So
>> the router sees it as an internal address trying to get in, and that's
>> not allowed.
>
>OK. Is there a trick I can use so that I can access this machine from
>inside AND outside our LAN using the same name?

I'm afraid that's beyond my ken.  My jury-rigged solution is to fire up
a dial-in account.  The only reason to do that has been to verify that
sub domains are resolving.  But, that's not what you're asking for, is
it?
-- 
gt                     kk5st@sbcglobal.net
I have never drunk so much that I passed out---
at least not that I can remember.