Errores En Vpn

VPN Client Error Messages - Reason from 401 to 436
Reason 401: An unrecognized error occurred while establishing the VPN connection.
Troubleshooting: VPN connection was not established because of an unrecognized reason. Please check client logs for details.
Reason 402: The Connection Manager was unable to read the connection entry, or the connection
entry has missing or incorrect information.Troubleshooting: Either the connection profile is missing or does not have all the information. To fix this problem, you can either select
another connection profile, or fix the current connection entry. Connection profiles are located in \profiles. On most
machines, this is C:\Program Files\Cisco Systems\VPN Client\profiles. To fix this problem, replace the connection profile file from theprofiles directory. This file can be copied from a machine that has the correct entry of this file.
Reason 403: Unable to contact the security gateway.
Troubleshooting: This can happen because of multiple reasons. One of the reasons that users can get this message is because IKE negotiations failed. Check the client logs for details. Also check this Cisco VPN Client Errors.
Reason 404: The remotepeer terminated the connection during negotiation of security policies.
Troubleshooting: Check the remote peer (head−end) logs to determine the cause for this failure. connection during negotiation of security policies.
Reason 405: The remote peer terminated connection during user authentication.
Troubleshooting: This reason is not currently used.
Reason 406: Unable to establish a securecommunication channel.
Troubleshooting: This reason is not currently used.
Reason 407: User authentication was cancelled by the user.
Troubleshooting: A user hit the cancel button (instead of OK) in the VPN Client user authentication dialog.
Reason 408: A VPN connection is already in the process of being established.
Troubleshooting: A connection is already in process.
Reason 409: A VPNconnection already exists.
Troubleshooting: A VPN connection already exists.
Reason 410: The Connection Manager was unable to forward the user authentication request.
Troubleshooting: This is not currently used.
Reason 411: The remote peer does not support the required VPN Client protocol.
Troubleshooting: The remote peer is either not a Cisco device or it does not support the VPN Client protocolspecification.
Reason 412: The remote peer is no longer responding.
Troubleshooting: 1. In many cases, this is due to loss of connectivity.  Make sure you can ping the remote peer, or check remote peer logs for why it is not responding to the client.
2. If you have your firewall turned on, there might be a rule that is preventing the connection from being established properly.  Disable yourfirewall and try again.
3. Please make sure the group name is exactly as the same as the VPN server group name.
4. Try disabling any firewall software on your PC.
5. Setting your MTU to 1300 or lower will prevent packets from being fragmented and therefore increase performance. To do that ,go to the Start>All Programs>Cisco Systems VPN Client>Set MTU.
Cisco VPN Client error - The remote peer is nolonger responding.
Reason 413: User authentication failed.
Troubleshooting: Either the user entered wrong user authentication information, or the client was not able to launch the XAuth (user authentication) process. Case: Secure VPN connection terminated locally. Reason 413: user authentication failed
Reason 414: Failed to establish a TCP
Troubleshooting: The VPN Client was not able toestablish the TCP connection for IPSec over TCP connection mode. Please try IPSec over UDP or straight IPSec. Please look at client logs for details.
Reason 415: A required component PPPTool.exe is not present among the installed client software.
Troubleshooting: Please make sure that ppptool.exe is present in the client installation directory (this is generally C:\Program Files\Cisco Systems\VPN...