• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 529
  • Last Modified:

NAT Problem on PIX

I am experiencing a maddening problem on our Cisco PIX:

When I setup a NAT rule to bind a global address to an internal server it closes all connectivity to that server. Thus, rather than allowing external data to pass to the internal server (access rule is also setup), it actually blocks that server from accessing external hosts.

Originally, we had this problem with hosts on the inside network, but not for hosts on the dmz. We wiped the setup and everything suddenly worked fine with the new setup.
This then completely stopped working when there was an IP address conflict on the external interface (my mistake) and nothing would go through at all.

So, third try, I have one server on the DMZ and it won't connect to the internet, it also will not be visible.

Perhaps important to note as well:
There is an implicit rule that controls access. However, when I create any type of other rule on the internal interface, the implicit rule stops functioning. I have to create a new rule to allow outgoing traffic. Is this normal?
I am starting to suspect your PIX is not working correctly. We are still using our old firewall until we can get this one to work.

This is our configuration (I changed the external IP addresses)

Building configuration...
: Saved
:
PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 100full
interface ethernet2 auto
interface ethernet3 auto shutdown
interface ethernet4 auto shutdown
interface ethernet5 auto shutdown
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 dmz security4
nameif ethernet3 intf3 security6
nameif ethernet4 intf4 security8
nameif ethernet5 intf5 security10
enable password ujZsBO8dBcra862y encrypted
passwd ujZsBO8dBcra862y encrypted
hostname tkypix1
domain-name company.com
clock timezone JST 9
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
name 172.16.1.31 DNS1
access-list outside_access_in permit tcp any host 111.111.111.111 eq domain
access-list inside_access_in permit tcp any host DNS2 eq domain
access-list inside_access_in permit tcp any any
pager lines 24
mtu outside 1500
mtu inside 1500
mtu dmz 1500
mtu intf3 1500
mtu intf4 1500
mtu intf5 1500
ip address outside 111.111.111.110 255.255.255.0
ip address inside 10.132.10.1 255.255.255.0
ip address dmz 172.16.1.1 255.255.255.0
no ip address intf3
no ip address intf4
no ip address intf5
ip audit info action alarm
ip audit attack action alarm
no failover
failover timeout 0:00:00
failover poll 15
no failover ip address outside
no failover ip address inside
no failover ip address dmz
no failover ip address intf3
no failover ip address intf4
no failover ip address intf5
pdm location 10.132.15.0 255.255.255.0 inside
pdm location 10.132.16.100 255.255.255.255 inside
pdm location 10.132.16.0 255.255.255.0 inside
pdm location 10.132.17.0 255.255.255.0 inside
pdm location 10.132.16.0 255.255.255.0 dmz
pdm location DNS2 255.255.255.255 dmz
pdm location 10.132.0.0 255.255.0.0 inside
pdm history enable
arp timeout 14400
global (outside) 10 interface
nat (inside) 10 0.0.0.0 0.0.0.0 0 0
static (dmz,outside) 111.111.111.111 DNS2 netmask 255.255.255.255 0 0
static (inside,dmz) 10.132.0.0 10.132.0.0 netmask 255.255.0.0 0 0
access-group outside_access_in in interface outside
access-group inside_access_in in interface inside
route outside 0.0.0.0 0.0.0.0 110.111.111.1 1
route inside 10.132.15.0 255.255.255.0 10.132.10.10 1
route inside 10.132.16.0 255.255.255.0 10.132.10.10 1
route inside 10.132.17.0 255.255.255.0 10.132.10.10 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 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 10.132.16.100 255.255.255.255 inside
http 10.132.16.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 10.132.16.0 255.255.255.0 inside
telnet 10.132.16.0 255.255.255.0 dmz
telnet 10.132.16.0 255.255.255.0 intf3
telnet 10.132.16.0 255.255.255.0 intf4
telnet 10.132.16.0 255.255.255.0 intf5
telnet timeout 5
ssh 10.132.16.0 255.255.255.0 inside
ssh timeout 5
console timeout 0
terminal width 80
Cryptochecksum:8de40ec21fcfd5e322a8376febfdadf8
: end
[OK]




0
wvanbesien
Asked:
wvanbesien
  • 3
1 Solution
 
lrmooreCommented:
>when I create any type of other rule on the internal interface, the implicit rule stops functioning. I have to create a new rule to allow outgoing traffic. Is this normal?
Correct. This is normal. Only one rule applied at a time implicit, or explicit..

Remove the acl from the inside interface until you can get everything working, then we can help you write a proper acl to make any restrictions that you want for outbound traffic..

>access-list outside_access_in permit tcp any host 111.111.111.111 eq domain
DNS uses UDP packets, not TCP packets. Should be:
   access-list outside_access_in permit udp any host 111.111.111.111 eq domain
                                                        ^^
0
 
wvanbesienAuthor Commented:
Hi,

I actually got it to work, but I don't know how. Obviously, I changed the access lists, all 6 servers are accessible now.  

Suddenly, traffic was allowed to flow and everything worked normal. Is there some sort of emergency lockdown system to blocks access incase there is a misconfiguration? At another time when I was configuring the rules, the PDM experienced some problem and suddenly all access was cut off. Reloading the PIX cleared it up.

0
 
lrmooreCommented:
Did you fix the access-list to allow UDP vs TCP for DNS?
You must have..
0
 
lrmooreCommented:
Are you still working on this?
Have you found a solution?
Do you need more information?

This question will be classified as abandoned soon if we don't get some feedback from you.

Can you close out this question? See here for details:
http://www.experts-exchange.com/help.jsp#hs5

Thanks for your attention!
0

Featured Post

A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now