Possible Cause: You do not have the required user rights to open and edit the file.

Action: Ensure that you have sufficient user rights. For details, refer to Section 3.1.2, Non-Root Access.

Possible Cause: The gateway name/ IP address is not valid.

Action: Specify a valid gateway name/IP address in the profile.

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:

Possible Cause: IKE is not running.

Action: Start IKE using the following command:

Possible Cause: Application error. For details, refer to Section A.2, Application Errors.

Action: Restart IKE using the following command:

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:

Possible Cause: Application error. For details, refer to Section A.2, Application Errors.

Action: Restart IKE using the following command:

Possible Cause: Application error. Refer to Section A.2, Application Errors.

Action: Restart IKE using the following command:

Possible Cause: Application error. Refer to Section A.2, Application Errors.

Action: Restart IKE using the following command:

Possible Cause: Server failed to respond. Either the server is not up or the network is down.

Action: Ensure that the server and network are up and running.

Possible Cause: IKE is down.

Action: As root, restart IKE using the following command:

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: The profile file uses an incorrect file format.

Action: Using the Profile Manager, re-create the profile. For details, refer to Section 3.2, Connection Profiles.

Possible Cause: The profile directory is not created or it is removed.

Action: Re-create the profile using the Profile Manager provided with the GUI. For details, refer to Section 3.2, Connection Profiles. By default, the profile gets created in the proper directory.

Possible Cause: The profile is missing.

Action: Re-create the profile using the Profile Manager provided with the GUI. For details, refer to Section 3.2, Connection Profiles.

Possible Cause: You have provided multiple parameters. Only one parameter is allowed at one instance.

Action: Provide one option at a time (for example vpnc -d). Only the command vpnc -v -c profile is allowed to have multiple parameters.

Possible Cause: You have provided more parameters than required.

Action: The CLI does not allow more parameters than required for the function. Refer to the Connecting to the Gateway Using a CLI or use vpnc -h before proceeding.

Possible Cause: You have used the verbose mode without specifying any other parameter.

Action: Verbose mode makes sense only when used along with other parameters. For options, refer to Section 3.3.3, Using the Command Line Utility. Specify the parameters as in the example vpnc -v -c profile for getting verbose details.

Possible Cause: The specified profile does not exist.

Action: Specify a valid profile. If no valid profile exists, create a new one using the Profile Manager provided with the GUI. For details, refer to Section 3.2, Connection Profiles.

Possible Cause: The specified profile is corrupt.

Action: Re-create the profile using the Profile Manager provided with the GUI. For details, refer to Section 3.2, Connection Profiles.

Possible Cause: The certificate path is not created or it is deleted.

Action: Re-create the certificate path /user's home directory/.turnpike/usercerts/ and copy the certificate to this path.

Possible Cause: Either the certificate is not valid or the password is incorrect.

Action: Verify the validity of the certificate and password. Relaunch the CLI and specify the correct certificate password.

Possible Cause: The specified profile is corrupt.

Action: Re-create the profile using the Profile Manager provided with the GUI. For details, refer to Section 3.2, Connection Profiles.

Possible Cause: IKE is not running, the server is not responding, or the network is down.

Action: Ensure that IKE, the server, and the network are up and running.

Possible Cause: The specified profile is not in the correct format.

Action: Re-create the profile using the Profile Manager provided with the GUI. For details, refer to Section 3.2, Connection Profiles.

Possible Cause: The gateway IP address you specified in the profile is not valid.

Action: Edit the profile (using the Profile Manager provided with the GUI) to specify the correct IP address/gateway name.

Possible Cause: You have specified an incorrect DNS name.

Action: Ensure that the DNS name you specified is valid.

Possible Cause: The network or the DNS server is down.

Action: Ensure that the network and the DNS server are up and running.

Possible Cause: The connection attempt failed.

Action: Check the IKE logs to find out the reason. For details, refer to Section A.1.3, IKE Log.

Possible Cause: There is no profile directory.

Action: Create a profile using the GUI. For details, refer to Section 3.2, Connection Profiles.

Possible Cause: You have specified an incorrect username, password, or both.

Action: Specify the correct username and password.