Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ASA Outside address overlap with static NAT, but where??

Status
Not open for further replies.

rocketlauncher

Programmer
Nov 11, 2000
110
US
Hello all,

We just got an Cisco ASA5510 and we have configured for internet and dmz, and that's working fine, but I tried to configure VPN client access based on cisco document and I get the following Info messsage when I try to configure the NAT (inside) 0 access-list comand:

INFO: Outside address overlap with static NAT configuration

I've checked and doublecheked and no network or ip address are overlapping, it's driving my insane. :(

I have three other sites with pixes and used the same type of configuration except for network and those kind of things and they're working fine.

My config is below.

Please help!

Thanks!
------------------------------------
MYHOSTANME(config)# show run
: Saved
:
ASA Version 7.1(2)
!
hostname MYHOSTANME
domain-name MYDOMAINNAME
names
!
interface Ethernet0/0
nameif outside
security-level 0
ip address OUTSIDE-ADDRESS 255.255.255.224
!
interface Ethernet0/1
nameif inside
security-level 100
ip address 172.16.13.1 255.255.255.0
!
interface Ethernet0/2
speed 100
duplex full
nameif dmz
security-level 50
ip address 172.16.12.1 255.255.255.0
!
interface Management0/0
shutdown
nameif management
security-level 100
no ip address
management-only
!
dns server-group DefaultDNS
domain-name MYDOMAINNAME
access-list 110 extended permit ip 172.16.13.0 255.255.255.0 192.168.20.0 255.255.255.0
pager lines 24
mtu outside 1500
mtu inside 1500
mtu dmz 1500
mtu management 1500
ip local pool VPN-POOL 192.168.20.20-192.168.20.35
icmp deny any outside
global (outside) 1 OUTSIDE-ADDRESS-2
nat (inside) 0 access-list 110
nat (inside) 1 172.16.13.0 255.255.255.0
static (inside,dmz) 172.16.13.0 172.16.13.0 netmask 255.255.255.0
route outside 0.0.0.0 0.0.0.0 70.234.6.193 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00
timeout mgcp-pat 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 RADIUS protocol radius
aaa-server RADIUS host RADIUS-SERVER
timeout 5
key radauth
aaa authentication ssh console LOCAL
aaa authentication serial console LOCAL
aaa authentication telnet console RADIUS
no snmp-server location
no snmp-server contact
end
------------------------------

Thanks,

Rocket
 
...hi rocketman
...let me try to get this thing rolling..soon others will join in...

its not because both are giving reference to 172.16.13.0..is it?
..seems like you could do it..
...for a test i would change one


nat (inside) 0 access-list 110 <---------------172.16.13.0
nat (inside) 1 172.16.13.0 255.255.255.0<-------172.16.13.0

access-list 110 extended permit ip 172.16.13.0 255.255.255.0 192.168.20.0 255.255.255.0


CCNP,CCSP,MCSE,Sec+,Net+,A+...
 
Hi Dan!

I actually ignored the error and everything is working fine. Also, searching on cisco forum found two people with the same situation, one after she upgraded form 6.0 to 7.x. and the other with the ASA. So I went with it and it worked.

But what you mention makes sense, I'll have to try that, just to see what happens. I'll let you know of the result.

As of know the Site to Site VPN is up and and running.

Thanks again Dan.

Rocket.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top