Boy, I'm sure people are getting sick of this discussion.
I have ONE user with a Mac at home. She's our Web Developer. She wants to RDP to her main computer (Windows) at the office.
We have an ASA 5510 running our VPN right now, and we're using the AnyConnect client to get all of our other users to connect, however she cannot get the 2.4.0202 client to work on her MAC. Keeps throwing kernel panics and dying.
I'm going to try the BETA 2.5 that is out there for the client, but if that doesn't work I'd like to fall back on Snow Leopard's built in IPSec VPN client.
My problem is that EVERY piece of documentation I have read about configuring that client talks about a group name and a shared secret key. This information is supposed to be contained in a .PCF file, but I have searched through new installs of the AnyConnect client, old installs of the AnyConnect client, exploded MSIs of the AnyConnect client package, and I cannot find a .PCF file anywhere.
I can only assume they are not used with this version of the client. But if that is the case, where do I find the information in our 5510 to fill in the blanks on her Mac?
A .pcf file is specific to the Cisco IPSec software client. This file is used to pre-populate or enable certain client-side features. In a traditional IPSec remote access configuration, the client is configured with a group name and pre-shared key. AnyConnect works a bit differently using either an alias or group URL to identifty a tunnel group. If no specific tunnel group is specified, the default WebVPN tunnel group will be matched and associated group policy attributes applied to the connection. AnyConnect has a profile feature in which an XML file is used to tweak client features. This can be likened to the legacy client .pcf file. You can read more about AnyConnect profiles at the link below.
As for your Mac OSX user, I would recommend that you uninstall the 2.4.202 client and either install the latest 2.4.1012 or 2.5 Beta clients for testing. Please document any errors that may occur with the latest client versions so that we can troubleshoot further.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR
and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity
options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in
HA DocumentationCode download linksGoalRequirementLimitationsSupported
ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationCo...
Question I am currently unable to specify "crypto keyring" command when
configuring VPN connection on my cisco 2901 router. The following
licenses have been activated on my router :