Using and Troubleshooting the Default.rcf File for Global VPN Clients

03/26/2020 14 12998

DESCRIPTION:
Using and Troubleshooting the Default.rcf File for Global VPN Clients

RESOLUTION:

Using and Troubleshooting the Default.rcf File for Global VPN Clients

The default.rcf file allows the SonicWall VPN Gateway administrator to create and distribute preconfigured VPN connections for SonicWall Global VPN Clients. The SonicWall VPN Gateway administrator can distribute the default.rcf file with the Global VPN Client software to automatically create preconfigured VPN connections for streamlined deployment. The VPN connections created from the default.rcf file appear in the Global VPN Client window. The Global VPN Client user simply enables the VPN connection and after XAUTH authentication with a username and password, the policy download is automatically completed.

How the Global VPN Client Uses the Default.rcf File
When the Global VPN Client starts up, the program always looks for the configuration file, Connections.rcf, in the C:UsersAppDataRoaming SonicWallGlobal VPN Client directory. If this file does not exist, the Global VPN Client looks for the default.rcf file in the program install directory, C:Program Files SonicWallGlobal VPN Client. The Global VPN Client reads the default.rcf file, if it exists and creates the configuration file, Connections.rcf, in the C:UsersAppDataRoaming SonicWallGlobal VPN Client directory. The Connections.rcf file contains all the VPN connection configuration information for the SonicWall Global VPN Client, with sensitive data (user names and passwords) encrypted.

Troubleshooting the Default.rcf File

Issue:
If there are any incorrect entries or typos in your default.rcf file, the settings in the default.rcf file will not be incorporated into the Global VPN Client, and no connection profiles will appear in the Global VPN Client window. The error message Failed to parse configuration will appear in the Global VPN Client Log Viewer, or the following error message will be displayed when attempting to import the file: "Could not import the specified configuration file. The file appears to be corrupt."
Solution:
Ensure that the file does not contain any non-ASCII characters. The Connections.rcf file created by the default.rcf file must be deleted from the directory and the default.rcf file edited to correct the errors.

Issue:
The default.rcf file cannot have an attribute of READ Only.
Solution:
The Connections.rcf file created by the default.rcf file must be deleted from the directory and the default.rcf file Read Only attribute removed to correct the error

Issue:
The Peer Name, displays the following error message when attempting to connect: "Failed to convert the Peer name to an IP address".
Solution:
When setting the Peer Name to the special case of , the tag for must be set to 1. The Connections.rcf file created by the default.rcf file must be deleted from the directory