From: George He (georgeh@adstream.com)
Date: Fri Feb 03 2006 - 02:18:16 GMT-3
Try clear the existing maps:
clear xlat
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
supernet
Sent: Friday, 3 February 2006 3:55 PM
To: 'Niche'
Cc: 'Cisco certification'; cisco@groupstudy.com
Subject: RE: PIX question
Thanks. The PIX took both commands but HTTP redirect doesn't work. It
also
gave a warning "mapped-address conflict with existing static". Any more
thoughts?
-----Original Message-----
From: Niche [mailto:jackyliu419@gmail.com]
Sent: Thursday, February 02, 2006 8:36 PM
To: supernet
Cc: Cisco certification; cisco@groupstudy.com
Subject: Re: PIX question
Hi there,
Remove "Static (dmz,outside) 69.31.3.2 69.31.3.2 netmask
255.255.255.255"
Then input "Static (dmz,outside) tcp 69.31.3.2 HTTP 69.31.3.2 8080
netmask 255.255.255.255" first,
finally, input "Static (dmz,outside) 69.31.3.2 69.31.3.2 netmask
255.255.255.255" again.
See if that's work, I don't have a PIX at home so can't verify for you.
Best Regards,
Jacky
On 2/3/06, supernet <supernet@comcast.net> wrote:
> We have a HTTP/FTP server in DMZ. The following configuration works
fine.
>
> Static (dmz,outside) 69.31.3.2 69.31.3.2 netmask 255.255.255.255
>
> We now have a requirement to have PIX redirect incoming HTTP traffic
to
port
> 8080 so I tried to add a command
>
> Static (dmz,outside) tcp 69.31.3.2 HTTP 69.31.3.2 8080 netmask
> 255.255.255.255
>
> However, the PIX gave an error message "duplicate of existing static".
Why
> is that? Any advice? By the way, we are not using NAT. Thanks. Yoshi
>
>
This archive was generated by hypermail 2.1.4 : Wed Mar 01 2006 - 11:28:17 GMT-3