Link to home
Start Free TrialLog in
Avatar of mattscaffa
mattscaffa

asked on

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.
SOLUTION
Avatar of JFrederick29
JFrederick29
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
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