Showing results for 
Search instead for 
Did you mean: 

Site to Site VPN with NAT

Level 1
Level 1


L2L VPN Tunnel to client’s remote networks.  I am required to NAT my private network to a publicly routable unique network.

Technical Information

Local network:

NAT to Network: 71.x.x.96 (Range provided by ISP)

Outside INT of ASA: 71.x.x.115

Remote Network:

Crypto ACL

access-list crypto extended permit ip 71.x.x.96

The tunnel comes up, but my internal hosts are unable to access the tunnel because I am not NAT’ing the inside to the NAT to addresses correctly.  Below is what I have tried. 

Use of Policy NAT

Access-list policy-nat extended permit ip

Static (inside,outside) 71.x.x.0 access-list policy NAT

This doesn’t work as when I show xlate, I show the following over and over again. 

Global 71.x.x.0 Local  It never translates the next host for example Global 71.x.x.97 Local  Traffic does not pass through the tunnel to allow access to the host.

If anyone can please help I would greatly appreciate it.  I’ve also found another possibility but not exactly sure how to implement it.

15 Replies 15


Try this to see if you can reach the other site:

access-list POLICYNAT permit ip

nat (inside) 1 access-list POLICYNAT

global (outside) 1 71.x.x.96

The crypto ACL you leave it as it is.

Check if you see packets being transmitted through the tunnel when you initiate traffic to 10.10.10.x

You can do this using:  sh cry ipse sa peer x.x.x.x   -->  x.x.x.x is the public IP of the other's site end of the tunnel.


Thank you for your help.  My job is on the line with this one....Very important new client.

Level 1
Level 1

?I'm not seeing the xlate for my internal to external. nor can I access resources on the other end.

You're encrypting the traffic when sending to

But you're not decrypting any.

This means, the other side of the tunnel is not responding or not sending the traffic back to you.

This is sometimes because they don't have a route to your network pointing in the right direction (assuming the default gateway won't do it).

Can you check if the other site, has the correct routes in place and that they are receiving your encrypted packets, and if so, if they are encrypting their packets back to you?  (Again, because you're not receiving any).


Yes I can do that.  I do have a question if you don't mind...  Should I see a translation for my host in the sho xlate?


You should see a translation when connecting from 192.168.1.x to 10.10.10.x

sh xlate should show you the translation being build.
This will happen before encryption, then the traffic will be encrypted and sent through the tunnel as it shows on the
sh cry ips sa peer x.x.x.x


When I do a show xlate the translation for the host I'm testing from does not show up.  Any idea what

could be causing that?

Could you post all static/nat & global commands you have in the firewall ?

Make sure you do a clear xlate when you change nat configurations.

static (inside,outside) tcp 71.x.x.116 smtp smtp netmask  dns
static (inside,outside) 71.x.x.117 netmask dns

global (outside) 1 interface
global (outside) 1 71.x.x.96 netmask

nat (inside) 0 access-list management_nat0_outbound_1 - Cisco VPN Client tunnel from remot access
nat (inside) 1 access-list policy-nat dns
nat (inside) 1 dns

Can you also post ACL: management_nat0_outbound_1 please.

I've attached my entire config I know something has to be wrong somewhere.  I'm no expert on this

and am going by documentation.  If you don't mind please review the config and tell me where I'm wrong.

Jennifer Halim
Cisco Employee
Cisco Employee

Sorry but you haven't configured the policy NAT suggested by Federico. Your configuration does not have that configured, and I also see different ip address range in your configuration than you originally requested.

Can you advise which subnet do you actually want to NAT and going to which remote subnet as again ip addressing are different to the one you specified initially.

I was trying not to show my config to much...  I got it working turned out my config was good.  However, I'm still not natting correctly.  It is using the PAT address of the outside interface to go through the tunnel instead of the range I specified.


Can you advise your latest nating statement?

sh run nat

sh run global

sh run static

and please also include the access-list from the above output.