We are using MS IAS (Radius) for all VPN authentication. Created the Secret key on both boxes and set the client name. In the groups you need to make it all or nothing. You can have a local group and a radius group, or the the Radius group will try to take the Group access Information and try to authenticate against it, thus leaving the connection never established. We set the group to Base Group to radius and it lets all users authenticate off of AD.
We are running a mixed bag. Most kerberos, but IT staff is using reverse encryption and all is working.
As far as the clos error. Active directory is the time server for al clients. Load Atomic Clock on the DC's and then tell the concentrator that one of the DC's is the NTP server. This should fix it as well as keep all your client machines up to date. Having a DC in Eastern time ad the concentrator in GMT will even mess it up, even though they have the same time they are really off.
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...