Re: Strange empty NAT entry

asaykao73 · ‎07-27-2009

Hi All,

What's causing some work stations to create this strange NAT entry with no protocol defined and no Outside local and Outside global.

core2#sh ip nat trans | inc 172.16.75.139

Pro Inside global Inside local Outside local Outside global

--- 210.15.240.9 172.16.75.139 --- ---

tcp 210.15.240.9:5380 172.16.75.139:5380 61.137.191.125:80 61.137.191.125:80

Any ideas?

Thanks.

Andy

Roman Rodichev · ‎08-05-2009

that a static NAT entry, look for "ip nat inside source static" in your config

regards,

Roman

asaykao73 · ‎08-05-2009

Hi Roman,

Thanks for the reply.

There is no static nat configured which is why I'm puzzled by that entry.

core2#sh run | inc nat

nat server

ip nat outside

ip nat inside

ip nat outside

ip nat inside

ip nat translation timeout 300

ip nat pool NAT-POOL 210.15.240.6 210.15.240.9 netmask 255.255.255.224

ip nat inside source route-map nonat pool NAT-POOL overload

route-map nonat permit 10

That's the whole config and you can see that there is no static nat configured anywhere.

I have a few dhcp clients doing this on the network.

Look for example at the dhcp clients of 172.16.75.23 and 172.16.75.239.

core2#sh ip nat trans

Pro Inside global Inside local Outside local Outside global

tcp 210.15.240.9:1024 172.16.75.239:49796 210.15.254.237:443 210.15.254.237:443

--- 210.15.240.8 172.16.75.23 --- ---

--- 210.15.240.9 172.16.75.239 --- ---

tcp 210.15.240.6:1024 172.16.75.26:49240 207.46.61.90:80 207.46.61.90:80

tcp 210.15.240.6:1025 172.16.75.243:50811 202.45.127.78:993 202.45.127.78:993

tcp 210.15.240.6:1032 172.16.75.232:51226 66.102.11.164:80 66.102.11.164:80

tcp 210.15.240.6:1026 172.16.75.232:51526 72.167.82.19:993 72.167.82.19:993

tcp 210.15.240.6:1027 172.16.75.241:49982 209.85.129.111:993 209.85.129.111:993

tcp 210.15.240.8:54775 172.16.75.23:54775 89.149.236.104:80 89.149.236.104:80

Thanks.

Andy