Possible Cause: The profile you chose for the VPN connection has an invalid certificate. Possibly, the profile is removed, renamed, or tampered with.
Action: Re-create the profile with another certificate. For details, refer to Section 3.2, Connection Profiles.
Possible Cause: You have not specified the IP address/gateway name.
Action: Specify the IP address/gateway name to proceed.
Possible Cause: The number of characters in the certificate name has exceeded the limit. Only 80 characters are permitted (including the pathname). For example, /home/user1/.turnpike/usercerts/mycert.pfx is treated as having 42 characters.
Action: Rename the certificate so that it adheres to the character limit.
Possible Cause: You have not specified the password.
Action: Specify the password.
Possible Cause: /user's home directory/.turnpike/usercerts/ does not contain the certificate file.
Action: Copy the certificate file in .pfx format to the path mentioned above.
Possible Cause: Either the certificate is not valid or the password is incorrect.
Action: Verify the validity of the certificate and password.
Possible Cause: The gateway name/IP address that you have specified is not valid.
Action: Specify a valid gateway name/IP address.
Possible Cause: Either the network or DNS server is down.
Action: Ensure that your network and DNS server are up and running.
Possible Cause: The profile file in XML format is corrupt.
Action: Using the Profile Manager, delete the profile and create a new one. For details, refer to Section 3.2, Connection Profiles.
Possible Cause: You have not specified the certificate password.
Action: Specify the certificate password.
Possible Cause: IKE is down.
Action: As root, restart IKE.
Possible Cause: IKE might be running, but you do not have sufficient user rights.
Action: Get access rights to use VPN Client. For details, refer to Section 3.1.2, Non-Root Access.
Possible Cause: IKE is down.
Action: Verify the IKE log for details. The log file can be accessed at /var/log/messages.
Possible Cause: IKE is down.
Action: Verify the IKE log for details. The log file can be accessed at /var/log/messages.
Possible Cause: Application error. For details, refer to Section A.2, Application Errors.
Action: Restart IKE using the following command:
/etc/init.d/racoon restart
Possible Cause: Server failed to respond.
Action: Verify the IKE log for details. The log file can be accessed at /var/log/messages.
Possible Cause: IKE is down.
Action: Verify the IKE log for details. The log file can be accessed at /var/log/messages.
Possible Cause: IKE is down.
Action: As root, restart IKE.
Possible Cause: The gateway name/IP address you have specified is not valid.
Action: Specify the correct gateway name/IP address.
Possible Cause: gmodule support is not available on your machine.
Action: Provide gmodule support to your machine. For details, refer to the GNOME developer Website .
Possible Cause: Issues with VPN Client installation.
Possible Cause: The help file is removed.
Action: Reinstall the VPN Client.
Possible Cause: Application error. For details, refer to Section A.2, Application Errors.
Action: Reinstall VPN Client.
Possible Cause: The format in which you specified the network details is not valid.
Action: Specify the details in the dotted IP address format (for example, 10.0.0.0).
Possible Cause: The format in which you specified the mask details is not valid.
Action: Specify the details in the dotted IP address format (for example, 255.0.0.0).
Possible Cause: The connection failed. There is no response after connection attempts for a period of time (more than five minutes).
Action: Check the IKE logs to find out the reason. For details, refer to Section A.1.3, IKE Log.
Possible Cause: You have specified an incorrect username, password, or both.
Action: Specify the correct username and password.
Possible Cause: The connection failed. There is no response from the VPN gateway.
Action: Ensure that the gateway is up and running.