Problem static NAT on 501

[kmcferrin]

First, the PIX is being used to connect two networks (both private) from different companies so that we can share data. We are both in the same building. From the PIX I can ping servers on both the inside and outside interfaces without problems.

I need to be able to initiate a connection on TCP port 9008 from the "outside" (10.10.3.0/24 and 172.30/16) to the "inside" (10.10.11.0/24). The 10.10.31.0/24 is another outside network that needs to be able to see the PIX (ping, etc) but not pass traffic.

I tried to set up a static NAT for port 9008 that forwards traffic from the outside to the 10.10.11.10 server on the inside, but I cannot make the connection. Does the config below look correct for this?

PIX Version 6.3(4)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password ****************** encrypted
passwd ****************** encrypted
hostname ********
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
access-list adt_out permit tcp host 172.30.14.204 host 10.10.3.250 eq 9008
access-list adt_out permit tcp host 172.30.14.217 host 10.10.3.250 eq 9008
access-list adt_out permit icmp any any
access-list adt_out permit tcp host 10.10.3.2 host 10.10.3.250 eq 9008
access-list adt_out permit tcp host 10.10.3.2 host 10.10.3.250 eq telnet
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 10.10.3.250 255.255.255.0
ip address inside 10.10.11.5 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
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 interface 9008 10.10.11.10 9008 netmask 255.255.255.
255 0 0
static (inside,outside) tcp interface telnet 10.10.11.5 telnet netmask 255.255.2
55.255 0 0
access-group adt_out in interface outside
route outside 10.10.31.0 255.255.255.0 10.10.3.242 1
route outside 172.30.0.0 255.255.0.0 10.10.3.242 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
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
telnet 10.10.3.0 255.255.255.0 outside
telnet 10.10.11.0 255.255.255.0 inside
telnet timeout 5
ssh 0.0.0.0 0.0.0.0 inside
ssh timeout 5
console timeout 0
terminal width 80
Cryptochecksum:***************************

 

[mbilgrav]

classical problem !

Once you have :
static (inside,outside) tcp interface 9008 10.10.11.10 9008 netmask 255.255.255.255 0 0

the interface command in that statement mean the IP OF THE OUTSIDE interface.
Hence it is THIS IP your application should point to on tcp/9008 !!

Hence you need to modify your outside ACL to macth this:

access-list adt_out permit tcp host 10.10.3.2 host 10.10.3.250 eq 9008
should be :
access-list adt_out permit tcp host 10.10.3.2 interface outside eq 9008

HTH
Martin

 

[kmcferrin]

I'll have to double-check and see if I ended up making that change. The system is now working as intended, and the biggest problem that I found was the company using the internal interface had a route incorrectly configured on their server on the inside.

I have a suspicion that it might work either way, since the 10.10.3.250 was the IP address of our outside interface.