NAT problems with PIX 501

Hi
I've been setting up a pix at home, and it works pretty good.
The only problem, is that NAT only works from one inside ip.
When trying from other ip's i get the following in syslog:
Oct 05 09:53:50 10.0.0.1 %PIX-3-305006: portmap translation creation
failed for udp src inside:10.0.0.10/1025 dst outside:*.*.4.24/53
I've compared my config with other config's that's supposed to work,
but I'm not able to spot the problem.
Anyone care to take a quick look?

Config:
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password * encrypted
passwd * encrypted
hostname pix
domain-name *.cc
clock timezone CEST 1
clock summer-time CEDT recurring last Sun Mar 2:00 last Sun Oct 3:00
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 10.0.0.3 Eureka
access-list outside_access_in permit tcp any interface outside eq 3389
log
access-list outside_access_in permit tcp any interface outside eq 8082
log
access-list outside_access_in permit tcp any interface outside eq 25000

access-list outside_access_in permit tcp any interface outside eq 3784
access-list outside_access_in deny tcp any any log
access-list outside_access_in deny udp any any log
access-list inside_access_in permit ip any any
pager lines 24
logging on
logging trap warnings
logging host inside *
icmp permit any echo-reply outside
icmp permit any echo outside
icmp permit any unreachable outside
icmp permit any echo-reply inside
icmp permit any echo inside
icmp permit any unreachable inside
mtu outside 1500
mtu inside 1500
ip address outside *.*.*.106 255.255.255.252
ip address inside 10.0.0.1 255.255.255.0
ip verify reverse-path interface outside
ip verify reverse-path interface inside
ip audit info action alarm
ip audit attack action alarm
pdm location Eureka 255.255.255.255 inside
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) interface Eureka netmask 255.255.255.255 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 *.*.*.105 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
ntp server * source outside prefer
http server enable
http 10.0.0.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
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
telnet timeout 5
ssh 10.0.0.0 255.255.255.0 inside
ssh timeout 30
console timeout 0
dhcpd address 10.0.0.2-10.0.0.15 inside
dhcpd dns * *
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
dhcpd enable inside
username admin password * encrypted privilege 2
terminal width 80

Re: NAT problems with PIX 501

wrote in message
news:1160035004.362370.270760@h48g2000cwc.googlegroups.com.. .
> Hi
> I've been setting up a pix at home, and it works pretty good.
> The only problem, is that NAT only works from one inside ip.
> When trying from other ip's i get the following in syslog:
> Oct 05 09:53:50 10.0.0.1 %PIX-3-305006: portmap translation creation
> failed for udp src inside:10.0.0.10/1025 dst outside:*.*.4.24/53
> I've compared my config with other config's that's supposed to work,
> but I'm not able to spot the problem.
> Anyone care to take a quick look?
>

> name 10.0.0.3 Eureka
> access-list outside_access_in permit tcp any interface outside eq 3389
> log
> access-list outside_access_in permit tcp any interface outside eq 8082
> log
> access-list outside_access_in permit tcp any interface outside eq 25000
>
> access-list outside_access_in permit tcp any interface outside eq 3784
> access-list outside_access_in deny tcp any any log
> access-list outside_access_in deny udp any any log



> static (inside,outside) interface Eureka netmask 255.255.255.255 0 0




It's because you only have 1 IP and you are using a 1 to 1 static. You need
to use PAT for that static.

Paste in the below:

clear xlate
no static (inside,outside) interface Eureka netmask 255.255.255.255 0 0
static (inside,outside) tcp interface 3389 Eureka 3389 netmask
255.255.255.255 0 0
static (inside,outside) tcp interface 8082 Eureka 8082 netmask
255.255.255.255 0 0
static (inside,outside) tcp interface 25000 Eureka 25000 netmask
255.255.255.255 0 0
static (inside,outside) tcp interface 3784 Eureka 3784 netmask
255.255.255.255 0 0
clear xlate
wr mem

Re: NAT problems with PIX 501

> It's because you only have 1 IP and you are using a 1 to 1 static. You
> need
> to use PAT for that static.

He has PAT configured.

global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0

Re: NAT problems with PIX 501

"chris" wrote in message
news:HJCdnfVbq7Q0qrjYRVny3w@eclipse.net.uk...
>
>> It's because you only have 1 IP and you are using a 1 to 1 static. You
>> need
>> to use PAT for that static.
>
> He has PAT configured.
>
> global (outside) 1 interface
> nat (inside) 1 0.0.0.0 0.0.0.0 0 0
>
>

Apparently you missed:
static (inside,outside) interface Eureka netmask 255.255.255.255 0 0
Make the global pat statement useless.

Re: NAT problems with PIX 501

"Brian V" wrote in message
news:T_WdnfjlJ_9I6LjYnZ2dnUVZ_oadnZ2d@comcast.com...
>
> "chris" wrote in message
> news:HJCdnfVbq7Q0qrjYRVny3w@eclipse.net.uk...
>>
>>> It's because you only have 1 IP and you are using a 1 to 1 static. You
>>> need
>>> to use PAT for that static.
>>
>> He has PAT configured.
>>
>> global (outside) 1 interface
>> nat (inside) 1 0.0.0.0 0.0.0.0 0 0
>>
>>
>
> Apparently you missed:
> static (inside,outside) interface Eureka netmask 255.255.255.255 0 0
> Make the global pat statement useless.
>
>

Errr no! You can still have statics and have PAT for everything else! For
example I have statics for my mail server and FTP server but everyone else
is PATed out using the above commands. Having a static NAT statement for one
host doesn't mean that PAT won't work for anything else. That would just be
silly wouldn't it?

Re: NAT problems with PIX 501

"Brian V" wrote in message
news:T_WdnfjlJ_9I6LjYnZ2dnUVZ_oadnZ2d@comcast.com...
>
> "chris" wrote in message
> news:HJCdnfVbq7Q0qrjYRVny3w@eclipse.net.uk...
>>
>>> It's because you only have 1 IP and you are using a 1 to 1 static. You
>>> need
>>> to use PAT for that static.
>>
>> He has PAT configured.
>>
>> global (outside) 1 interface
>> nat (inside) 1 0.0.0.0 0.0.0.0 0 0
>>
>>
>
> Apparently you missed:
> static (inside,outside) interface Eureka netmask 255.255.255.255 0 0
> Make the global pat statement useless.
>
>

On my Pix ..

static (inside,outside) globalmail mailhost netmask 255.255.255.255 0 0
static (inside,outside) globalsrv srv netmask 255.255.255.255 0 50

nat (inside) 1 0.0.0.0 0.0.0.0 0 0
global (outside) 1 interface

So I static NAT for two hosts on the network and then the rest of the
network gets PATed to the outside address. This is a quite a normal set up
and certainly having statics does not "make the global pat statement
useless"!

Chris.

Re: NAT problems with PIX 501

"chris" wrote in message
news:Lr2dnf8GrcdVHbjYRVnygQ@eclipse.net.uk...
>
> "Brian V" wrote in message
> news:T_WdnfjlJ_9I6LjYnZ2dnUVZ_oadnZ2d@comcast.com...
>>
>> "chris" wrote in message
>> news:HJCdnfVbq7Q0qrjYRVny3w@eclipse.net.uk...
>>>
>>>> It's because you only have 1 IP and you are using a 1 to 1 static. You
>>>> need
>>>> to use PAT for that static.
>>>
>>> He has PAT configured.
>>>
>>> global (outside) 1 interface
>>> nat (inside) 1 0.0.0.0 0.0.0.0 0 0
>>>
>>>
>>
>> Apparently you missed:
>> static (inside,outside) interface Eureka netmask 255.255.255.255 0 0
>> Make the global pat statement useless.
>>
>>
>
> On my Pix ..
>
> static (inside,outside) globalmail mailhost netmask 255.255.255.255 0 0
> static (inside,outside) globalsrv srv netmask 255.255.255.255 0 50
>
> nat (inside) 1 0.0.0.0 0.0.0.0 0 0
> global (outside) 1 interface
>
> So I static NAT for two hosts on the network and then the rest of the
> network gets PATed to the outside address. This is a quite a normal set up
> and certainly having statics does not "make the global pat statement
> useless"!
>
> Chris.
>

Chris,
You are missing the HUGE fact that he only has 1 IP address. It is assigned
on the outside of his firewall. When you have a single IP you cannot do 1 to
1 NAT's. You must do PAT's on everything including your static statements.
In your pix/asa you have a minimum of 3 IP's, one on your outside interface,
one thats mapped to globalmail and one thats mapped to globalsvr.
-Brian

Re: NAT problems with PIX 501

Brian V skrev:
> It's because you only have 1 IP and you are using a 1 to 1 static. You need
> to use PAT for that static.
>
> Paste in the below:
>
> clear xlate
> no static (inside,outside) interface Eureka netmask 255.255.255.255 0 0
> static (inside,outside) tcp interface 3389 Eureka 3389 netmask
> 255.255.255.255 0 0
> static (inside,outside) tcp interface 8082 Eureka 8082 netmask
> 255.255.255.255 0 0
> static (inside,outside) tcp interface 25000 Eureka 25000 netmask
> 255.255.255.255 0 0
> static (inside,outside) tcp interface 3784 Eureka 3784 netmask
> 255.255.255.255 0 0
> clear xlate
> wr mem

That was the trick, thanks alot.

Re: NAT problems with PIX 501

"Brian V" wrote in message
news:0vmdnVwFCqwEDrjYnZ2dnUVZ_sidnZ2d@comcast.com...
>
> "chris" wrote in message
> news:Lr2dnf8GrcdVHbjYRVnygQ@eclipse.net.uk...
>>
>> "Brian V" wrote in message
>> news:T_WdnfjlJ_9I6LjYnZ2dnUVZ_oadnZ2d@comcast.com...
>>>
>>> "chris" wrote in message
>>> news:HJCdnfVbq7Q0qrjYRVny3w@eclipse.net.uk...
>>>>
>>>>> It's because you only have 1 IP and you are using a 1 to 1 static. You
>>>>> need
>>>>> to use PAT for that static.
>>>>
>>>> He has PAT configured.
>>>>
>>>> global (outside) 1 interface
>>>> nat (inside) 1 0.0.0.0 0.0.0.0 0 0
>>>>
>>>>
>>>
>>> Apparently you missed:
>>> static (inside,outside) interface Eureka netmask 255.255.255.255 0 0
>>> Make the global pat statement useless.
>>>
>>>
>>
>> On my Pix ..
>>
>> static (inside,outside) globalmail mailhost netmask 255.255.255.255 0 0
>> static (inside,outside) globalsrv srv netmask 255.255.255.255 0 50
>>
>> nat (inside) 1 0.0.0.0 0.0.0.0 0 0
>> global (outside) 1 interface
>>
>> So I static NAT for two hosts on the network and then the rest of the
>> network gets PATed to the outside address. This is a quite a normal set
>> up and certainly having statics does not "make the global pat statement
>> useless"!
>>
>> Chris.
>>
>
> Chris,
> You are missing the HUGE fact that he only has 1 IP address. It is
> assigned on the outside of his firewall. When you have a single IP you
> cannot do 1 to 1 NAT's. You must do PAT's on everything including your
> static statements. In your pix/asa you have a minimum of 3 IP's, one on
> your outside interface, one thats mapped to globalmail and one thats
> mapped to globalsvr.
> -Brian
>

Brian,

Yes, I missed that. I thought that he had two addresses and had a static for
one.

Sorry. You are quite correct.

Chris.