I made the change on the client's xml profile before making a connection. But it appears that the xml profile gets overwritten during the Anyconnect connection and from the default profile on the ASA. Is it possible to change the one on the PC to allow this without making a change globally to the profile on the ASA?
Is it possible to retain the connection and have someone else log on to machine? The reason I ask is that our level 2 support would like to be able to sign in as the local admin of the workstation to make changes or look at things. The general user popluation does not have admin rights.
If you are making changes to the client profile on the client machine then whenever you make a connection to the ASA, the ASA will push the xml profile which will replace the existing xml profile i.e. it will replace the changes that you made to the xml profile because the changes were made on the client machine and not on the ASA. You need to make this change on the XML profile binded to the group-policy on the ASA and then only new profile will take effect.
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...