You have three options.1) Use packet-tracer and see why it fails or if it does really pass.2) Create the NAT using ASDM and let it figure out the syntax for you.3) Use DNS as this is what it was designed for.
nat (Inside, Outside) 1 source static 10.0.0.0 [ip address to NAT source address to] destination static [ip address/subnet of destination] 172.2.2.2 service HTTP HTTP no-proxy-arpIf you want truly any service rather than just HTTP as the original ser...
The use of multiple contexts and VPN will not work as one issues would be how to split the licensing up across them? If the license allows 200 and you have 10 contexts, you can't get 200 for everyone of them and 20 may not work either. So, VPN doe...
You could do that as you can create a NAT to look at the source and destination IP's as well as the service, you can either then change none, one, two or all three of those in the NAT rule.A better solution, use DNS. All of the clients should be poi...
It is a total of 300Mbps; so it could be 200/100, 150/150, 100/200, 1/299, etc. If they really think they will be using the full pipe in both directions, they could bump up to the 5520. That 300Mbps also says "up to" and that is the key there. In...
