Cisco Vpn Authentication Error 413
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us
Cisco Vpn Client Error 413 User Authentication Failed
Learn more about Stack Overflow the company Business Learn more about hiring developers cisco vpn client reason 413 authentication failed or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question
Cisco Vpn Authentication Methods
and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted cisco vpn authentication active directory up and rise to the top How to troubleshoot Cisco VPN Client Authentication Error 413? up vote 3 down vote favorite I'm a software developer contractor, and I've been given Cisco VPN access to a customer's network. It's a typical set up, using an RSA SecureID soft token, and I'm successfully able to connect through VPN Client (v 5.0.07.0440) when I run it within a VirtualBox instance (Win cisco vpn error 412 7) on my development workstation. However, when I run VPN Client directly on the development workstation's OS itself (also Win 7), it has been failing, and gives me Authentication Error 413. That error is normally attributed to bad credentials having been entered, and every troubleshooting reference I've found points to user error being the only possible cause. Yet I'm certain that's not the issue here, as I can easily prove to myself when using the VPN Client on the VM and changing nothing else. I'm at a loss as to what that relevant difference is between the two environments. Any guidance would be appreciated. Log from VPN Client follows. (I've redacted specific server & IP values and replaced them with {text}.) Cisco Systems VPN Client Version 5.0.07.0440 Copyright (C) 1998-2010 Cisco Systems, Inc. All Rights Reserved. Client Type(s): Windows, WinNT Running on: 6.1.7601 Service Pack 1 1 15:54:10.121 01/24/14 Sev=Info/4 CM/0x63100002 Begin connection process 2 15:54:10.132 01/24/14 Sev=Info/4 CM/0x63100004 Establish secure connection 3 15:54:10.132 01/24/14 Sev=Info/4 CM/0x63100024 Attempt connection with server "{server name}" 4 15:54:10.139 01/24/14 Sev=Info/6 IKE/0x6300003B Attempting to establish a connection with {IP}. 5 15:54:10.144 01/24/14 Sev=Info/4 IKE/0x63000001 Starting IKE Phase 1 Negotiation 6 15:54:10.284 01/24/14 Sev=Info/6 GUI/0x63B00012 Authentication
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help
Cisco Vpn Error 414
Create a Freelance Project Hire for a Full Time Job Ways cisco vpn error 401 to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor
Secure Vpn Connection Terminated Locally By The Client Reason 413 User Authentication Failed
Services Groups Website Testing Store Headlines Experts Exchange > Questions > Cisco VPN Authention : Reason - 413 Want to Advertise Here? Solved Cisco VPN Authention : Reason - http://serverfault.com/questions/569765/how-to-troubleshoot-cisco-vpn-client-authentication-error-413 413 Posted on 2008-07-30 Hardware Firewalls IPsec Software Firewalls 5 Verified Solutions 22 Comments 4,853 Views Last Modified: 2011-10-19 Hi I need some help regarding cisco vpn client authentication. We have a vpn concentrator and a cisco acs. This is how it is done... The user database is created on the cisco acs and the group names are https://www.experts-exchange.com/questions/23609014/Cisco-VPN-Authention-Reason-413.html created on the vpn concentrator. This is what happens.... When I connect to the vpn concentrator using the cisco client, it gets authenticated and I am asked to enter the username and password. When i enter the username and password which has been created on the cisco acs, I get the following error: Secure VPN Client terminated locally by the client. Reason 413: User authentication failed. Can you tell me if i need to change any settings on the cisco acs???? Note : The test between the vpn concentrator and the cisco acs is successful. There are 2 authentication servers for the time being. (1) Internal VPN database (Placed TOP) and (2) Radius Server(Cisco ACS- Placed Second). Please advice Thanks 0 Question by:Merlin_Raja Facebook Twitter LinkedIn Google LVL 10 Best Solution bykoudry Hi Merlin_Raja, I found this the following article useful, although the software and components are not exactly the same. It does explain the concepts and basics to get things going. http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00800b6099.shtml#configuringthemicrosoftserverwithias Go to Solution 22 Comments LVL 10
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire https://www.experts-exchange.com/questions/23893144/Cisco-VPN-client-and-error-413-user-authentication-failed-with-RSA-SecurID.html for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Cisco VPN client and error 413 (user authentication failed) with RSA SecurID Want to Advertise Here? Solved Cisco VPN client and error 413 (user authentication failed) with RSA cisco vpn SecurID Posted on 2008-11-10 VPN Cisco 1 Verified Solution 4 Comments 11,596 Views Last Modified: 2012-05-05 I have an ASA 5510 that I use to provide VPN access to my HQ network. The authentication for the VPN users is handled by an RSA SecurID appliance. Ever since we started using SecurID for auth (we previously used AD) we've had some issues with the cisco vpn authentication auth failing if you try to connect more than once. For example, if I connect to VPN it works fine, but if I disconnect and attempt to reconnect, it immediately gives me error 413 - user authentication failed. If I close the VPN client and relaunch it, it will work again. This also happens if I launch the VPN client, click connect, press cancel when it prompts for auth, and then click connect again...instead of prompting for auth, it immediately says auth failed. Again, closing and relaunching the VPN client is all that is needed to resolve the issue, but a lot of our users don't think to try this, so it leads to a lot of calls to the helpdesk. If we use AD for auth, this problem goes away, so it must be something to do with the SecurID system and the way the ASA talks to it. We're running version 5.0.00.0340 of the Cisco IPSec VPN client, and the same problem also occurs with version 4.6. We use the SDI auth protocol between the ASA and SecurID appliance. We have support agreemen