Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I'm working on setting up a backup link for our ASA 5505 and I've followed these directions: http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00806e880b.shtmlThe backup ISP gives us a dynamic address, however...
I've been over the many other posts on this issue, and they all seem a little different, so I started my own thread.I have deployed AnyConnect 3.1.02026 to my users via the ASA, and we all get the Untrusted VPN Server Cert warning when connecting.Whe...
I was able to get this to work on my VPN 3000, but after installing the new ASA last night, I am unable to do the following:User logs into WebVPN and attempst to access our CMS over a tunnel that is up on our ASA. All the appropriate acls are present...
We are using a 3005 Concentrator and everything was working just dandy up until last week. VPN clients were connecting and authenticating using Kerberos/AD and they were able to access all resources on our connected networks. All client related conne...
I have 2 L2L tunnels set up with two outside contractors. I am using a 3005 device and the tunnels are up and active. Each contractor is able to pass traffic to my local network (ping devices on our private IP) however I am not able to get to their l...
Additional info: I noticed that the CAcert.org CA cert that I installed is associated with Trustpoint3, while the new Identity Certificate is associated with TrustPoint2. Is this the problem? How do I associate the CA cert from CAcert.org with TrustP...
I created a public cert using CACert.org, installed it, and I'm still getting the "Certificate is from an untrusted source" error. This is progress, but it still requires the user to check the trust box and then connect. The higher-ups want it to be ...
I followed all the directions, but unfortunately I'm still getting the warning. This time it gives me the correct FQDN in the warning, so I'm not really sure what the problem is. It still says that the cert is untrusted.Any other ideas?Thanks.
