I am rather new to administrating the ASA. I am currently on 8.2.5 but I will be moving to 8.4.3 within the next week or so. In the meantime I would like to get my vpn system up and going. Currently I am able to vpn in to my system using a local server group, but I would like to simplify things by getting my ASA to accept AD credentials. I found a bunch of articles referencing how to do this. I first attempted to use this article but the test option yeilds a failure stating "The authentication Server not responding: AAA Server has been removed." I then began to do more research finding things like having to add the Network Policy and Access Services to my domain controllers which I vaguely remember using at my last job prior to getting our Tacacs+ server.
Here are my questions:
Is LDAP able to be used for this process with AD 2008 Domain Controllers? I have a feeling the linked article I referenced used old AD 2003 servers because I am fairly sure I followed it to a T.
Is LDAP the preferred method to connect the ASA to the directory server? Is NPAS a better option? I would like to use a Tacacs+ server but I don't have that option right now and probably won't for another year.
Does anyone have a good link to some documentation that shows this method (preferred/best practice method)?
Thanks in advance. I did some searching on the forums and there were some mildly related items to what I am asking but I couldn't find anything very recent. If someone's search-fu is better then mine, linking me to a relevant already asked question would be helpful as well.
Update 1: The login dn notation in the linked article is wrong. Format should be domain\username or username@domain. Once I corrected this issue, the test began working.
I have now created the IPSec Connecktion Profile, Group Policy, and Dynamic Access Policy. I have setup my PCF file on my client to connect to the new group I created, however I seem to be getting the following errors:
Cisco Systems VPN Client Version 5.0.07.0440
Copyright (C) 1998-2010 Cisco Systems, Inc. All Rights Reserved.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...