*Use ping test to ensure the host is reachable from outside
*chk ACL using 'sh access-list outside_access_in' to verify incoming traffic hitcount
This can help you to eliminate 'feature' related issue, like using name instead of IP, and direct mapping instead of 'port redirection' format. I used to do this when I first configure the firewall. Once everthing confirm working fine, then only I used the 'fancy' features.
If it's really caused by a bug, the above should not working as well. But it's worth to try.
I am having this same issue with 7.2(1) on a 515E, I would try and create access-list / static's in the same format as you show here only I did not use any names... and for some reason they would not "turn on" even after clear xlate ...etc they did start to work after a bit but I was confused for a long period.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...