Very old problem. Tunnel comes up I am able to ping and connect any host from ASA inside network to Sonicwall insidenetwork but I am not able to connect any host from Sonicwall network to ASA inside network. Pind is even not working. I know i see many geeks around should solve this preety quickly.
It is possible that there is more than one problem. But the first issue that I notice is the access list applied to your outside interface:
access-list inbound extended permit icmp any any echo-reply access-list inbound extended permit icmp any any unreachable access-list inbound extended permit icmp any any time-exceeded
access-group inbound in interface outside
With this access list I wonder that the tunnel comes up. And since it permits echo-reply but does not permit echo, then it would allow the network at the peer to respond to ping but not allow them to initiate ping.
Fix the issue with the access list and then let us know what happens.
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...