• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3683
  • Last Modified:

Cisco VPN Client - Error 413 cannot authenticate user

I have about 10 VPN clients connecting to a Cisco ASA 5510. I am getting calls that sometimes people are getting 413 errors here and there. When they put in username and password, the dialog box pops up again and then they get a error 413 cannot authenticate. Any ideas, they are IPsec tunnels which I have 250 available liscenses.
2 Solutions
What version of Cisco client are you using?  You may want to try upgrading to 5.0.03 or higher.  I've run into this running 5.0.00 and using securID.  Using RSA/SecurID by chance?
mattscaffaAuthor Commented:
I have tried the latest and also 4.6. and still not authenticating. I now think it is a local issue with her laptop. No one else is having this problem.
I had  two cases in which the Client (v4.8) generated reason 413 (with correct username and passphrase):
- earlier this year it was a computer which did not meet firewall policy (the firewall software has been damaged and had to be reinstalled).
- yesterday it was token issue. The RSA token has desynchronized with RSA SecurID server and had to be resynchronized with the assistance of the VPN helpdesk. I wouldn't have figured it out without help as Cisco VPN Client haven't shown any warnings or errors (all options in the log settings were set to high priority).

BTW: our manual says, that there are few reasons for error 413 to appear:
- locked AD or token account
- dropped connection (which has to timeout before making another one)
- firewall and antivirus policy mismatch

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now