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. > > > >I have this network configuration > > > > E > > | > >Internet > > | > > | (EXT-IP) > >** R ** (Firewall) > > | (192.168.1.1) > >___|___ > >| | | | > >M S M M > > > > > >E: external machine > >R: router firewall for our intranet > >S: internal server running Linux (in fact it runs Mandrake 9.0) > >M: internal machines > > > 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? Would be handy for CVS configuration (which for example keeps information in CVS/Root) Jerome -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
