B.1 GUI Messages

This section explains some of the common GUI error messages that you come across while working with Novell BorderManager 3.9 VPN client.

Certificate not found. Ensure that the certificate is available.

Possible Cause: The profile you chose for the VPN connection has an invalid certificate. Possibly, the profile was removed, renamed, or tampered with.
Action: Re-create the profile with another certificate. For details, refer to Section 4.3, Connection Profiles.

Enter gateway name/IP address.

Possible Cause: You have not specified the IP address or gateway name.
Action: Specify the IP address or gateway name.

The certificate name is too lengthy. Rename the certificate 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.

Enter the password.

Possible Cause: You have not specified the password.
Action: Specify the password.

Certificate not found. Ensure that the certificate is available.

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 given above.

Failed to read certificate.

Possible Cause: Either the certificate is not valid or the password is incorrect.
Action: Verify the validity of the certificate and password.

Gateway name or IP address is not valid.

Possible Cause: The gateway name or IP address that you have specified is not valid.
Action: Specify a valid gateway name or IP address.

Server address error: Failed to resolve the DNS name. Retry after some time.

Possible Cause: Either the network or DNS server is down.
Action: Ensure that your network and DNS server are up and running.

Cannot read profile. Re-create the profile.

Possible Cause: The profile file in XML format is corrupt.
Action: Use the Profile Manager to delete the profile and create a new one. For details, refer to Section 4.3, Connection Profiles.

Profile is not valid.

Possible Cause: You have not specified the certificate password.
Action: Specify the certificate password.

Failed to connect to IKE. Restart IKE.

Possible Cause: IKE is down.
Action: As root, restart IKE.
Action: Verify the IKE log for details. The log file can be accessed at /var/log/messages.
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 4.1.2, Non-Root Access.
Possible Cause: Application error. For details, refer to Section A.2, Application Errors.
Action: Use the following command to restart the IKE: /etc/init.d/racoon restart
Possible Cause: The server failed to respond.
Action: Check the IKE log for details. The log file can be accessed at /var/log/messages.

IKE failed to respond. The client is exiting.

Possible Cause: IKE is down.
Action: Check the IKE log for details. The log file can be accessed at /var/log/messages.
Action: As root, restart IKE.

Gateway name or IP address is not valid.

Possible Cause: The gateway name or IP address you have specified is not valid.
Action: Specify the correct gateway name or IP address.

Failed to meet system requirements.

Possible Cause: gmodule support is not available on your machine.
Action: Provide gmodule support for your machine. For details, refer to the GNOME developer Web site .

Unable to locate the help file. Reinstall the client.

Possible Cause: Issues with VPN Client installation.
Possible Cause: The help file was removed.
Action: Reinstall the VPN Client.

Profile directory does not exist. Client installation might be incomplete.

Possible Cause: Application error. For details, refer to Section A.2, Application Errors.
Action: Reinstall the VPN Client.

Invalid Network. Re-enter.

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).

Invalid Mask. Re-enter.

Possible Cause: A possible cause of the problem.
Action: What can be done to resolve the problem.

Time-out occurred while waiting for a connection response from gateway. The client is exiting.

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.

Authentication Failed. Verify your credentials.

Possible Cause: You have specified an incorrect username, password, or both.
Action: Specify the correct username and password.

Gateway is not responding. The client is exiting.

Possible Cause: The connection failed. There is no response from the VPN gateway.
Action: Ensure that the gateway is up and running.