501 will not NAT using zoneedit

[Paul.Lane]

I have a 501 in front of my soho. It's runnig 6.2(2) I'm using cable modem and it gives my outside interface an IP dynamically. I use the "zoneedit" free dynamic DNS. This service will always point my web site to the correct IP, so it should allow me to host a web site on a server behind the PIX. I added the following 3 rules:

access-list inbound permit tcp any host xxx.xxx.xxx.xxx eq www

access-group inbound in interface outside

static (inside,outside) xxx.xxx.xxx.xxx 192.168.1.10 netmask 255.255.255.255 0 0

When I add the third rule,

I can no longer get out to the internet. It seems like I cannot nat.

Any ideas what I'm doing wrong.

Thanks

[mhoda]

Hello Paul,

What you need to do is Port redirection here ..

no static (inside,outside) xxx.xxx.xxx.xxx 192.168.1.10 netmask 255.255.255.255

static (inside,outside) tcp xxx.xxx.xxx.xxx www 192.168.1.10 www netmask 255.255.255.255 0 0

If PIX doesn't accept the last line, please replace xxx.xxx.xxx.xxx with keyword "interface".

After that please execute "clear xlate" and you would be good to go.

Regards,

Mynul

[Paul.Lane]

Hi Mynul,

Thank you for replying. I added the rule above and the PIx took. I also cleared the xlate and still nothing.

Below is a copy of my config:

: Written by enable_15 at 20:53:25.310 EDT Wed Jul 2 2003

PIX Version 6.3(1)

interface ethernet0 auto

interface ethernet1 100full

nameif ethernet0 outside security0

nameif ethernet1 inside security100

enable password encrypted

passwd encrypted

hostname

domain-name

clock timezone EST -5

clock summer-time EDT recurring

fixup protocol ftp 21

fixup protocol h323 h225 1720

fixup protocol h323 ras 1718-1719

fixup protocol http 80

fixup protocol ils 389

fixup protocol pptp 1723

fixup protocol rsh 514

fixup protocol rtsp 554

fixup protocol sip 5060

fixup protocol sip udp 5060

fixup protocol skinny 2000

fixup protocol smtp 25

fixup protocol sqlnet 1521

names

access-list 101 permit tcp any host xx.xx.xxx.xx eq pptp

access-list 101 permit gre any host xx.xx.xxx.xx

pager lines 24

logging host inside 192.168.1.10

mtu outside 1500

mtu inside 1500

ip address outside dhcp setroute

ip address inside 192.168.1.1 255.255.255.0

ip audit info action alarm

ip audit attack action alarm

pdm location 192.168.1.5 255.255.255.255 inside

pdm location 192.168.1.10 255.255.255.255 inside

pdm logging informational 100

pdm history enable

arp timeout 14400

global (outside) 1 interface

nat (inside) 1 0.0.0.0 0.0.0.0 0 0

static (inside,outside) tcp xx.xx.xxx.xx www 192.168.1.10 www netmask 255.255.25

5.255 0 0

timeout xlate 0:05:00

timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00

timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00

timeout uauth 0:05:00 absolute

aaa-server TACACS+ protocol tacacs+

aaa-server RADIUS protocol radius

aaa-server LOCAL protocol local

http server enable

http 192.168.1.0 255.255.255.0 inside

no snmp-server location

no snmp-server contact

snmp-server community public

no snmp-server enable traps

floodguard enable

telnet 192.168.1.5 255.255.255.255 inside

telnet 192.168.1.10 255.255.255.255 inside

telnet timeout 5

ssh timeout 5

console timeout 0

dhcpd address 192.168.1.11-192.168.1.33 inside

dhcpd lease 3600

dhcpd ping_timeout 750

dhcpd auto_config outside

dhcpd enable inside

terminal width 80

Cryptochecksum:xxxxxx

Thanks for you help

[wasonce_2000]

Paul,

Try changing your static command to the following. This will force the use of

the global address of the Interface and resolve any overlapping address conflict .

static (inside,outside ) interface 192.168.1.10 netmask 255.255.255.255 0 0

[wasonce_2000]

Paul,

Try changing your static command to the following. This will force the use of

the global address of the Interface and resolve any overlapping address conflict .

static (inside,outside ) interface 192.168.1.10 netmask 255.255.255.255 0 0

[mhoda]

Hi Paul,

The above is going to override the global pool hence traffic from inside using PAT/global will have issue. Only host 192.168.1.10 would be able to go out.

Is x.x.x.x a routable ip address? is it same as outside interface ip address that you are getting dynamically? If its the same ip address as interface, please add the line with "interface" keyword as suggested in my earlier pool.

Regards,

Mynul