Help with Cisco PIX 506e Firewall Access Rule and NAT config

[Epsil0n00]

Hey all,
I need to configure a PIX 506E to allow incoming connections from WAN, using HTTP, HTTP and TerminalSvcs (3389), to a single host (Win Srv 2008 with IIS7).

Network setup:
WAN: Single static IP
LAN Server address: 192.168.1.1

I currently have 3 NAT policies translating the external IP (which is the WAN interface IP) to the LAN Host (192.168.1.1). Each policy is in charge of translation for a different service (HTTP, HTTPS, or Terminal Svcs.

In the Access Rules I have a single incoming access rule allowing all services (all ports) from the WAN interface IP to 192.168.1.1.

Here's the odd part: incoming RDP connections are working great... however, I can't establish HTTP or HTTPS connections to the default IIS7 welcome page through the PIX. I can access the default web page internally from the LAN, on both HTTP and HTTPS... so I know the website is running. I don't think that I am being blocked by an IIS IP restriction as I don't get an IIS access denied page. When I attempt to contact the server via HTTP/s I just get a 'page not found' error.

Could someone more familiar with PIX configs look over my config and see if everything is setup properly?

Building configuration...
: Saved
:
PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password * encrypted
passwd * encrypted
hostname pixfirewall
domain-name ciscopix.com
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
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
fixup protocol tftp 69
names
object-group service SERVERservices tcp
port-object eq www
port-object eq 3389
port-object eq https
access-list outside_access_in permit tcp any interface outside
access-list inside_outbound_nat0_acl permit ip any 192.168.1.192 255.255.255.224
access-list outside_cryptomap_dyn_20 permit ip any 192.168.1.192 255.255.255.224
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 209.*.*.110 255.255.255.0
ip address inside 192.168.1.251 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool POOLNAME 192.168.1.200-192.168.1.210
pdm location 209.*.*.78 255.255.255.255 outside
pdm location 192.168.1.0 255.255.255.0 inside
pdm location 192.168.1.1 255.255.255.255 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_outbound_nat0_acl
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) tcp interface www 192.168.1.1 www netmask 255.255.255.255 0 0
static (inside,outside) tcp interface 3389 192.168.1.1 3389 netmask 255.255.255.255 0 0
static (inside,outside) tcp interface https 192.168.1.1 https netmask 255.255.255.255 0 0
access-group outside_access_in in interface outside
route outside 0.0.0.0 0.0.0.0 209.*.*.1 1
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 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
http server enable
http 209.*.*.78 255.255.255.255 outside
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
sysopt connection permit-ipsec
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto dynamic-map outside_dyn_map 20 match address outside_cryptomap_dyn_20
crypto dynamic-map outside_dyn_map 20 set transform-set ESP-3DES-MD5
crypto map outside_map 65535 ipsec-isakmp dynamic outside_dyn_map
crypto map outside_map interface outside
isakmp enable outside
isakmp policy 20 authentication pre-share
isakmp policy 20 encryption 3des
isakmp policy 20 hash md5
isakmp policy 20 group 2
isakmp policy 20 lifetime 86400
vpngroup VPN address-pool POOLNAME
vpngroup VPN dns-server 192.168.1.10
vpngroup VPN wins-server 192.168.1.10
vpngroup VPN default-domain domain.com.local
vpngroup VPN idle-time 1800
vpngroup VPN password ********
telnet timeout 5
ssh timeout 5
console timeout 15
terminal width 80
Cryptochecksum:******
: end
[OK]

 

[rathsach]

That's a bit odd.. Looks ok to me.. Try to remove fixup on http and see if that doesn't help.. It should ofcourse work with Fixup running, but try it anyway..

Any reason why you don't use the service group you made any more?

 

[drebo]

I would say that the issue likely stems from the fact that you're advertising the PIX's internal HTTP server on your outside interface IP address as well. I'm not sure which would take precidence.

A way to check would be to (from outside your network) try https://(ipaddress). If you get your PIX screen, then that's the issue.

 

[Epsil0n00]

Originally posted by: rathsach
That's a bit odd.. Looks ok to me.. Try to remove fixup on http and see if that doesn't help.. It should ofcourse work with Fixup running, but try it anyway..

Any reason why you don't use the service group you made any more?

Thanks for your response.
I will try turning off 'fixup' on HTTP traffic... but I need to learn how to do that first--I am a n00b when it comes with Cisco CLI commands.

I created that service group while I was testing and just haven't removed it yet.

Eps.

 

[Epsil0n00]

Originally posted by: drebo
I would say that the issue likely stems from the fact that you're advertising the PIX's internal HTTP server on your outside interface IP address as well. I'm not sure which would take precidence.

A way to check would be to (from outside your network) try https://(ipaddress). If you get your PIX screen, then that's the issue.

From outside the network I went to http://<ip_address> and https://<ip_address> and it did not load the PIX Device Manager screen... just the aforementioned default 'page not found' error.

Eps.

 

[drebo]

Page not found? I missed that. Is that giving you an HTTP 404 error or is it unable to find the site?

If it's a 404 error, your issue is with your IE configuration (are you using virtual hosts?). If it's unable to find the site, then the issue is likely in the NAT. One thing you could do is load up wireshark on the server and observe your incoming HTTP requests while someone is testing. Also, check the IE7 logs. This could be an IE7 misconfiguration.

 

[ScottMac]

Don't forget to "clear xlate" after putting any changes in the the ACL or NAT.

 

[rathsach]

Is it running Pix 7 or newer? You could try to connect via the ASDM and do a packet trace, see what it says..

Well spotted with the http server.. I'd try to disable that just in case that's what's making it all FUBAR..

 

[Epsil0n00]

Originally posted by: drebo
Page not found? I missed that. Is that giving you an HTTP 404 error or is it unable to find the site?

If it's a 404 error, your issue is with your IE configuration (are you using virtual hosts?). If it's unable to find the site, then the issue is likely in the NAT. One thing you could do is load up wireshark on the server and observe your incoming HTTP requests while someone is testing. Also, check the IE7 logs. This could be an IE7 misconfiguration.

No, it's not a 404 error, or any other IIS error, such as IIS 403.6 forbidden IP error, etc. I just get the standard IE "Internet Explorer cannot display the webpage" error... like I typed in the hostname incorrectly or something. I am pretty confident that the traffic is not making it through the PIX to the server.

 

[Epsil0n00]

Originally posted by: rathsach
Is it running Pix 7 or newer? You could try to connect via the ASDM and do a packet trace, see what it says..

Well spotted with the http server.. I'd try to disable that just in case that's what's making it all FUBAR..

No, the PIX is running 6.3.
Dumb question: is there anyway to disable the HTTP management interface on the WAN from the GUI?