Assuming that this is the scenario (attached file), then I see that the internal interface ip address and external ip address (assigned ip) are of the same range. Ideally this should work because of subnetting however it is always recommended to use a different range of ip's in the vpn pool so as to identify local subnet and remote subnet.
Another thing that you can try is that you can check if you are able to ping inside interface of the ASA. If you are not able to ping inside interface then run this command on the ASA "show run man" and it will show you whether management access is enabled on inside interface or not. If it is not enabled then enable it by running command "man inside" and then try to ping it again. If you are getting some error while enabling management access on inside interface then try to disable management access from any other interface because on ASA we can have management access enabled on one interface only.
Please give it a shot and let me know. If this does not work then I will need output of these two commands so as to fix this issue:
show run all group-policy vpnpolicy
show run nat
show crypto ipsec sa (capture this output once you are connected to the ASA using VPN)
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...