PIX 515e From a 506e

[GrantThomas]

Hello, I am having a small issue.

We had a 506e running and we decided to get get a 515e with DMZ, so for testing purposes I set the 515e up like the 506e, but added the DMZ to it. I tested everything internally and it works just fine, but the outside can not reach the webserver. The webserver for testing reasons is not on the DMZ right now, the DMZ is running a test webserver though, but nothing is plugged into it right now. I wanted to get normal operation working first.
Internally everyone can access the internet, but not the website by using the websites IP or domain. Not sure if I need to run the clear (XLATE,Local,ARP). So since reduce downtime I put the 506e backup untill I have more testing time. Any suggestions?

PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 auto
interface ethernet2 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 DMZ security30
enable password XXXXX encrypted
passwd XXXXX encrypted
hostname web-pix
domain-name XXXX
fixup protocol dns maximum-length 512
no fixup protocol ftp 21
no fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol http 81
fixup protocol ils 389
fixup protocol pptp 1723
no fixup protocol rsh 514
no fixup protocol rtsp 554
no fixup protocol sip 5060
fixup protocol sip udp 5060
no fixup protocol skinny 2000
no fixup protocol smtp 25
no fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list inbound permit tcp any host 24.X.X.211 eq www
access-list inbound permit tcp any host 24.X.X.211 eq https
access-list inbound permit udp any host 24.X.X.211 eq 443
access-list inbound permit tcp any host 24.X.X.212 eq www
access-list inbound permit tcp any host 24.X.X.212 eq https
access-list inbound permit udp any host 24.X.X.212 eq 443
access-list inbound permit tcp any host 24.X.X.213 eq www
access-list inbound permit tcp any host 24.X.X.213 eq https
access-list inbound permit udp any host 24.X.X.213 eq 443
access-list inbound permit tcp any host 24.X.X.222 eq pptp
access-list inbound permit tcp any host 24.X.X.214 eq 81
access-list inbound permit tcp any host 24.X.X.214 eq www
access-list inbound permit tcp any host 24.X.X.215 eq www
access-list inbound permit tcp any host 24.X.X.215 eq https
access-list inbound permit udp any host 24.X.X.215 eq 443
access-list dmz permit icmp any any
access-list dmz permit tcp any host 10.0.0.11 eq 1433
pager lines 24
logging on
logging trap informational
mtu outside 1500
mtu inside 1500
mtu DMZ 1500
ip address outside 24.X.X.210 255.255.255.240
ip address inside 192.168.1.191 255.255.255.0
ip address DMZ 10.0.0.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location 192.168.1.171 255.255.255.255 inside
pdm location 192.168.1.173 255.255.255.255 inside
pdm location 192.168.1.179 255.255.255.255 inside
pdm location 192.168.1.182 255.255.255.255 inside
pdm location 192.168.1.183 255.255.255.255 inside
pdm location 192.168.1.185 255.255.255.255 inside
pdm location 192.168.1.0 255.255.255.0 DMZ
pdm location 24.X.X.222 255.255.255.255 outside
pdm location 10.0.0.10 255.255.255.255 DMZ
pdm location 10.0.0.10 255.255.255.255 inside
pdm location 192.168.1.184 255.255.255.255 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
global (DMZ) 1 10.0.0.20-10.0.0.50 netmask 255.255.255.0
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
nat (DMZ) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) 24.X.X.211 192.168.1.179 netmask 255.255.255.255 0 0

static (inside,outside) 24.X.X.212 192.168.1.185 netmask 255.255.255.255 0 0

static (inside,outside) 24.X.X.213 192.168.1.171 netmask 255.255.255.255 0 0

static (inside,outside) 24.X.X.222 192.168.1.182 netmask 255.255.255.255 0 0

static (inside,outside) 24.X.X.215 192.168.1.183 netmask 255.255.255.255 0 0

static (inside,DMZ) 10.0.0.11 192.168.1.184 netmask 255.255.255.255 0 0
static (DMZ,outside) 24.X.X.215 10.0.0.10 netmask 255.255.255.255 0 0
access-group inbound in interface outside
access-group dmz in interface DMZ
route outside 0.0.0.0 0.0.0.0 24.X.X.209 1
timeout xlate 3:00: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 sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
aaa-server authinbound protocol radius
aaa-server authinbound max-failed-attempts 3
aaa-server authinbound deadtime 10
aaa-server authinbound (outside) host 24.X.X.222 cisco timeout 5
http server enable
http 192.168.1.0 255.255.255.0 inside
http 192.168.1.173 255.255.255.255 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
sysopt connection permit-ipsec
sysopt connection permit-pptp
telnet 192.168.1.0 255.255.255.0 inside
telnet 192.168.1.0 255.255.255.0 DMZ
telnet timeout 5
ssh timeout 5
console timeout 0
vpdn group 1 accept dialin pptp
vpdn group 1 ppp authentication pap
vpdn group 1 ppp authentication chap
vpdn group 1 ppp authentication mschap
vpdn group 1 ppp encryption mppe 40
vpdn group 1 client configuration dns 192.168.1.173 192.168.1.177
vpdn group 1 client configuration wins 192.168.1.173
vpdn group 1 client authentication aaa authinbound
vpdn group 1 pptp echo 60
vpdn enable outside
terminal width 80

 

[Supergrrover]

You have conflicting statics

static (inside,outside) 24.X.X.215 192.168.1.183 netmask 255.255.255.255 0 0

static (DMZ,outside) 24.X.X.215 10.0.0.10 netmask 255.255.255.255 0 0

You can only have one per IP address unless you are doing it by port.



Brent
Systems Engineer / Consultant
CCNP, CCSP

 

[GrantThomas]

Thanks for pointing that out for the DMZ, didnt see that for some odd reason, but the IP that isnt working is the static maipping of this:

static (inside,outside) 24.X.X.212 192.168.1.185 netmask 255.255.255.255 0 0

The .212 will not work it is not on the DMZ at all.

 

[Supergrrover]

All this seems correct. Couple of quick questions -
Where is the DNS resolution handled?
Can you get to it by the internal IP?
Can the server get out to the internet?
Can you post your old 506 config for comparison?


Also -
This ACL won't work like you think
access-list dmz permit tcp any host 10.0.0.11 eq 1433
An ACL applied to the DMZ interface only restricts traffic entering the pix from the DMZ. You will need to make the restrictions on the INSIDE and OUTSIDE interfaces.


Brent
Systems Engineer / Consultant
CCNP, CCSP

 

[GrantThomas]

DNS is handled by a win2k server.
I can access the server through the internall address.
The server can go out to the internet.
The 506 Config is the same minuz the adds to the DMZ.

Im not trying to tet the DMZ as of yet. just need the operation to function correctly then ill start the testing. Not sure why it would be blocking outside users to a basic route to a webserver.

ACL I put that inplace so the 10.0.0.10 DMZ would talk to the database server internally.

static (inside,DMZ) 10.0.0.11 192.168.1.184 netmask 255.255.255.255 0 0

 

[GrantThomas]

Solved the issue: It was the craziest thing ever. Basically what I did was change the outside IP to the webserver IP, then CLEAR XLATE then changed it back tot the real outside IP and it fixed all issues.

 

[Supergrrover]

That is odd. The config looked correct. Had you restarted it after changes before?


Brent
Systems Engineer / Consultant
CCNP, CCSP

 

[GrantThomas]

Yeah everything was restarted including the servers, I thought it was a bit odd as well.