- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2012 09:15 AM - edited 03-11-2019 04:22 PM
Hello everyone,
Could someone help me with this issue:
5 Jun 22 2012 10:07:48 305013 50.96.132.209 Asymmetric NAT rules matched for forward and reverse flows; Connection for icmp src outside2:68.153.135.201 dst fwinside:54.92.134.220 (type 8, code 0) denied due to NAT reverse path failure
I keep getting tis error on my ASA considering that I dont even have NAT rules for that source and destination, do you have any idea what whould the problem be?
Thanks
Solved! Go to Solution.
- Labels:
-
NGFW Firewalls
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2012 01:45 PM
Hello Yasaman,
There is definetely a nat statement causing this issue.
I would have to take a look at the Nat statement in order to solve it.
Senior Network Security and Core Specialist
CCIE #42930, 2xCCNP, JNCIP-SEC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2012 04:55 AM
Hi Yasaman,
The nat-control is enabled on the firewall,thats why you need a translation to allow the specific traffic.
To work , add a nat-exempt from the source to destination/ destination to source.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2012 01:45 PM
Hello Yasaman,
There is definetely a nat statement causing this issue.
I would have to take a look at the Nat statement in order to solve it.
Senior Network Security and Core Specialist
CCIE #42930, 2xCCNP, JNCIP-SEC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2012 04:55 AM
Hi Yasaman,
The nat-control is enabled on the firewall,thats why you need a translation to allow the specific traffic.
To work , add a nat-exempt from the source to destination/ destination to source.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2012 06:43 AM
Thank you,
The problem was a dynamic NAT rule. I added a NAT exempt and everything worked fine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-25-2012 10:17 AM
Hello Yasaman,
Great to hear that everything worked fine.
Please mark the question as answered so future users can learn from this topic.
Regards,
Julio
Senior Network Security and Core Specialist
CCIE #42930, 2xCCNP, JNCIP-SEC
