Re: Cisco PIX 501: Can't ping global IP-Adress from NATed IP
- From: roberson@xxxxxxxxxxxx (Walter Roberson)
- Date: Fri, 05 May 2006 09:41:06 GMT
In article <op.s82dvexp7mx1hz@localhost>,
Michael Schuberl <cisco_pix@xxxxxxxx> wrote:
Well there already is a DNS on that network, will that be sufficient?
Will the PIX be able to translate the lookup-requests then and substitute
the external for the internal adress? (that "alias"-thing, right?)
To my mind, the DNS resolves the request to the external IP. Therefore,
the client will again try to communicate with that address and the PIX
would still not able to translate that IP to the internal IP.
Have the internal DNS server hand out the internal address, and
on the 'static' statement for the server, add the 'dns' keyword. Then
when -external- hosts do a query, the PIX will translate the
internal IP to the external IP as the DNS response goes out of the
network.
The reason why I didn't want to set up an DNS is my lack of experience
with such services and it seems that some costume software we use simply
isn't using the gethostbyname() function and is therefor doomed to use IPs.
If the software can be configured to use the internal IPs for the
servers, then configure the DNS and static as noted above and everything
will be fine. [If the software is also used from outside your LAN,
then configure the external hosts to use the public IP.]
My task is to put that PIX infront of the nodes. The first thing I learned
back then was: it is not possible to force the PIX to behave in a
transparent way (e.g. just filter and foreward the traffic for
x.x.x.0-x.x.x.15 - without NAT), or did I configure something wrong?
The PIX 501 is fine with using the same address internally and externally.
The catch is that the two interfaces cannot have the same IP subnet,
so the external interface must be part of a different subnet and
your WAN router must route the public range to to the IP address
of the external interface. This is often done by arranging a
"carrier network" with your ISP -- a distinct /30 or /29 network that is
there just to allow your WAN equipment to talk to the ISP so
that the ISP can route the main network to you.
.
- Follow-Ups:
- Re: Cisco PIX 501: Can't ping global IP-Adress from NATed IP
- From: Michael Schuberl
- Re: Cisco PIX 501: Can't ping global IP-Adress from NATed IP
- References:
- Cisco PIX 501: Can't ping global IP-Adress from NATed IP
- From: Michael Schuberl
- Re: Cisco PIX 501: Can't ping global IP-Adress from NATed IP
- From: Michael Schuberl
- Re: Cisco PIX 501: Can't ping global IP-Adress from NATed IP
- From: Walter Roberson
- Re: Cisco PIX 501: Can't ping global IP-Adress from NATed IP
- From: Michael Schuberl
- Cisco PIX 501: Can't ping global IP-Adress from NATed IP
- Prev by Date: Re: Cat 6500 - weird boot behaviour
- Next by Date: Re: PEAP trouble
- Previous by thread: Re: Cisco PIX 501: Can't ping global IP-Adress from NATed IP
- Next by thread: Re: Cisco PIX 501: Can't ping global IP-Adress from NATed IP
- Index(es):
Relevant Pages
|