Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
we have a ASA 5520 and vpn coming in to the inside which works fine. We also have our management interface that is connected to the same network that our ipml is connected to. How do we allow vpn users to get to this network? interface Management0/0 ...
I have an issue where two rules get mixed and I'm not sure how/why or if I'm looking at the right place. We have 3 customers that connect to our firewall (5520) over VPN but they only want to use a external ip so we use NAT. This was working for one ...
I'm trying to setup a tunnel from our Cisco 5520 to a 5550 using one of our external ips natted through this tunnel. For some reason traffic that should hit this tunnel goes through global nat. Here is the configs I have for this tunnel:access-list p...
I'm pulling my hair our at this point so I'm hoping someone can see whats wrong... (4 weeks of cisco experience... )I have a tunnel that I want looking like so: / --> boston tunnelinternal > N...
Thank you everyone that looked at this issue BUT this was all me... I started looking at my logs and did not understand why the Deny TCP had a no connection.. then I figured it out... Our core router had a route back to the ASA for our VPN network bu...
Hi Marvin,So I'm looking at that but our firewall is only running 8.2.5 so we are in the before category and here is another datapoint when I'm on my vpn client pinging a node thats on the 'management' network I get that reply BUT when I do a telnet ...
I was reading this http://www.mikespicer.net/wp/cisco/cisco-vpn-multiple-or-overlapping-l2l-tunnels-using-nat/ article and one thing is telling me that i'm doing my setup wrong. He said you should not have more than two inside/NAT lines. And that if ...
Anyone? All are set to splitacl but even when I remove that and use no acl I still get the wrong route. Too me it looks like I'm leaving my fw with the correct NAT but it allways hits global (outside) 2 6.8.99.170 netmask 255.255.255.255 coming home....
I tried removing the vpn-filter for one of the tunnels or changing to a different access-list but still the same. My question is, why are there two NATs in my packet-tracer? and Why is the second showing a different ip for the outside?tpfw01# sh run ...
