Certificate passwords do not match. Enter the same password in both text boxes.
The New Password and Confirm Password fields of the Import Certificate dialog must both contain the same values.
Unable to create certificate enrollment request.
The VPN Client was unable to create an enrollment request to enroll the certificate with a certificate authority.
Certificate enrollment failed, or was not approved.
The certificate enrollment request failed or was not approved by the certificate authority.
Certificate is not valid, or not an online enrollment request.
The user attempted to resume enrollment of a certificate that is not valid or does not have a pending enrollment request.
Passwords do not match. Try again.
The value entered in the Confirm new password dialog did not match the value entered in the Enter new password dialog when attempting to change a certificate password.
Change password for certificate %1 failed.
The VPN Client was unable to change the password for the certificate.
Failed to load ipseclog.exe.
The VPN Client was unable to launch the ipseclog.exe application. Log messages will not be saved to the log file.
Unable to stop service/daemon.
The VPN Client was unable to stop the service/daemon. The service/daemon may be hung or there is a problem with the system's service/daemon management.
GI_VPNStop failed. Unable to disconnect.
The VPN Client failed to send a stop request for terminating the VPN connection to the service/daemon. The service/daemon may be stopped, hung, or not running. Communication with the service/daemon may have failed.
Service/daemon is not running.
The VPN Client service/daemon is not running. VPN connections cannot be established/terminated via the GUI.
IPC socket allocation failed with error %1h.
The VPN Client failed to create an inter-process communication socket in order to communicate with the service/daemon. VPN connections cannot be established/terminated via the GUI. Refer to Related Information for link to search on Cisco bug ID CSCed05004.
IPC socket deallocation failed with error %1h.
The VPN Client failed to close an inter-process communication socket that is used to communicate with the service/daemon while terminating. Subsequent use of the GUI may be unable to communicate with the service/daemon.
Secure connection to %1 was unexpectedly dropped.
The VPN connection was lost due to something other than termination by the VPN Client GUI. The connection could have been terminated by the user via the CLI, or internet connectivity may have been lost.
The authentication passwords do not match. Enter the same password in both text boxes.
The user was asked to enter a new authentication password in the extend authentication dialog and did not enter the same values into the New Password and Confirm Password fields. Both fields must contain the same values.
The authentication PINs do not match. Enter the same PIN in both text boxes.
The user was asked to enter a new authentication PIN in the extend authentication dialog and did not enter the same values into the New PIN and Confirm PIN fields. Both fields must contain the same values.
Unable to start the VPN connection.
The VPN Client failed to send a start request for establishing the VPN connection to the service/daemon. The service/daemon may be stopped, hung, or not running. Communication with the service/daemon may have failed.
An unrecognized error occurred while establishing the VPN connection.
VPN connection was not established because of an unrecognized reason. Please check client logs for details.
The Connection Manager was unable to read the connection entry, or the connection entry has missing or incorrect information.
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 FilesCisco SystemsVPN Clientprofiles. To fix this problem, replace the connection profile file from the profiles directory. This file can be copied from a machine that has the correct entry of this file.
Unable to contact the security gateway.
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.
The remote peer terminated the connection during negotiation of security policies.
Check the remote peer (head-end) logs to determine the cause for this failure.
The remote peer terminated connection during user authentication.
This reason is not currently used.
Unable to establish a secure communication channel.
This reason is not currently used.
User authentication was cancelled by the user.
A user hit the cancel button (instead of OK) in the VPN Client user authentication dialog.
A VPN connection is already in the process of being established.
A connection is already in process.
A VPN connection already exists.
A VPN connection already exists.
The Connection Manager was unable to forward the user authentication request.
This is not currently used.
The remote peer does not support the required VPN Client protocol.
The remote peer is either not a Cisco device or it does not support the VPN Client protocol specification.
The remote peer is no longer responding.
The remote peer is not responding to the client's request to establish the connection. Make sure you can ping the remote peer, or check remote peer logs for why it is not responding to the client.
User authentication failed.
Either the user entered wrong user authentication information, or the client was not able to launch the XAuth (user authentication) process.
Failed to establish a TCP connection.
The VPN Client was not able to establish the TCP connection for IPSec over TCP connection mode. Please try IPSec over UDP or straight IPSec. Please look at client logs for details.
A required component PPPTool.exe is not present among the installed client software.
Please make sure that ppptool.exe is present in the client installation directory (this is generally C Program FilesCisco SystemsVPN Client. If this file is not present, uninstall and reinstall the client.
Remote peer is load balancing.
The peer has advised you to use a different gateway.
The required firewall software is no longer running.
The required firewall is not running.
Unable to configure the firewall software.
The peer sent an unrecognized firewall message.
No connection exists.
This is an unexpected error. Please check client logs for details.
The application was unable to allocate some system resources and cannot proceed.
The system ran out of memory. If you think the system has enough memory, reboot the machine and try again.
Failed to establish a connection to your ISP. Failed to establish a dialup connection.
View the client logs for details.
Lost contact with the security gateway. Check your network connection.
The machine's IP address changed or the machine is no longer connected to the Internet.
Note The VPN Client is required to disconnect the VPN tunnel for security reasons, if the machines IP Address has changed.
Your VPN connection has been terminated.
Either the user disconnected the VPN tunnel, or there was an unexpected error.
Connectivity to Client Lost by Peer.
Connection disconnected by the peer. Check the peer logs for details.
Manually Disconnected by Administrator.
Administrator manually disconnected the VPN tunnel.
Maximum Configured Lifetime Exceeded.
The VPN Client exceeded the maximum configured lifetime for a session. This value is configured on the peer (head-end) device.
Unknown Error Occurred at Peer.
Peer disconnected tunnel. Check the peer logs for details.
Peer has been Shut Down.
Peer was shut down.
Unknown Severe Error Occurred at Peer.
Check the peer logs for details.
Configured Maximum Connection Time Exceeded.
VPN Client has been connected for longer than allowed by the peer.
Configured Maximum Idle Time for Session Exceeded.
The VPN connection was idle for longer than the time allowed by the administrator.
Peer has been Rebooted.
The peer has been rebooted.
Reason Not Specified by Peer.
The peer gave no reason for disconnecting the tunnel. Check the peer logs for details.
Policy Negotiation Failed.
Client and peer policies do not match. Try changing peer policies (try using 3DES, AES, and so forth) and then try again.
Firewall Policy Mismatch.
Firewall policies do not match with what was configured by the peer.
Certificates used have Expired.
The certificate used in the connection profile has expired. Update the certificate configured in the client profile, and then try again.
The necessary VPN sub-system is not available. You can not connect to the remote VPN server.
The VPN Client GUI has detected that it cannot communicate with the client service/daemon. The service/daemon may be stopped, hung, or not running. Communication with the service/daemon may have failed. Uninstall the VPN Client(see Related Information for link) and the anitvirus on the computer, then reinstall the VPN Client.
If you disable this feature, the %1 will not automatically disconnect your VPN connection when you logoff. As a result, your computer may remain connected after logoff.
The user has disabled the Disconnect VPN connection when logging off setting of the Windows Logon Properties dialog.
You do not have write privileges for this connection entry. It will be opened read-only.
The user is attempting to modify a connection entry whose file attributes have been set to read only.
The certificate %1 associated with this Connection Entry could not be found. Please select a different certificate or click Cancel.
The user is attempting to modify a connection entry that has a certificate associated with it. But the certificate associated with the profile was not found. It could be that the certificate lives on a smart card which is not connected to the system right now. Therefore, hitting cancel is a valid option.
You must use a Smart Card with this connection. Please insert the Smart Card before attempting a connection.
This warning means that the current profile requires the use of smart card, and no smart card is present on the system. The user should insert the correct smart card and should re-connect, or the user should select a different profile to connect.