Trying to get a Mac OS X client working with Clean Access. Got the agent loaded however everytime we try to authenticate it prompts with an error about communication issues and says that if we are using a temporary certificate (which we are) we need to add the certificate file to KeyChains. We've added the certificates however we still cannot logon. A windows client logs in no problem. Any ideas?
heys - for the OSX agents, verify on the CAS that you are not using an ip address for the self-signed cert. The cert must have a fqdn of the CAS(cas1.domain.com) instead of an ip. also dont forget to verify that the dns record exists for that entry. hope that helps
jvr775 - Yeah, that is what we thought the original problem was so we regenerated all the self-signed certs to use FQDNs based on the DNS records. All devices are pointing to the same DNS server and everything resolves names to IP and IP to names correctly. I've uploaded the error message that we are getting from the MAC client. In addition we've added the new certs to the MAC's X509Ancors Keychains and still no luck.
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...