From the output below it shows the client is configured for AES encryption and SHA hashing whereas the router is configured for 3DES and MD5. The proposals need to match for ISAKMP SA to be established.
ISAKMP:(0:0:N/A:0):Checking ISAKMP transform 1 against priority 5 policy
This is exactly what puzzeled me here as well. try to remove the isakmp policy and reapply it once more, maybe as well disable and enable isakmp on the interface before trying again to connect with the client.
because from the debugs it is mentioning that the policy doesn't have pre-shared enabled, while the configuration clearly states that it is enabled.
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...