Qbik Helpsys

Creating a hosted VPN

Configuring a WinGate VPN Node to host a VPN is a relatively simple process. If you have not done so, we recommend you read the Hosting a WinGate VPN overview, so you a familiar with the requirements and considerations for creating a hosted VPN.


In order to host a VPN, the VPN Service must be installed. If it is not installed, there will be an installation button available on the VPN Panel which allows you to do this. Alternatively the VPN Service can be installed from the Services panel, located at Control Panel > Services in the WinGate Management console.

To host a WinGate VPN :

  1. Open the WinGate Management console on the WinGate VPN Node machine that will host the VPN.

  2. Navigate to Monitoring > VPN to open the VPN Panel.
  3. Right click on the VPN Panel and select Host a VPN from the menu. This will open the Host VPN configuration.

  4. Enter in the Name field an easy to remember name for your VPN. (The name of your network or location is usually a good choice). This will be the name that remote VPN Nodes will have to specify in their configurations when attempting to join this VPN.

  5. In the Description field, enter a description of the nature and purpose of the VPN. This field is not mandatory but it is provided for ease of reference.
  6. On the Certificate drop down menu, select a WinGate certificate that is to be used by this VPN. Alternatively, click the Generate button to construct the certificate that will be associated with this VPN. Please refer to the Certificates helpfile on creating certificates in WinGate.
  7. In the Encryption Schema drop down menu, select either Strong or None to determine how WinGate VPN will encrypt data that travels through the tunnel (It is recommended that you always choose Strong for maximum security).
  8. Select the option on the Local Participation drop down menu to determine how the VPN will share the VPN Host network.

    • No local participation

      This network does not participate in the VPN. The VPN Host machine will only act as an intermediator between various remote VPN Client Nodes (and their networks) who wish to communicate with each other via the VPN.

    • Local machine only

      Only the VPN Host machine will participate in the VPN.

    • Local network

      This VPN Host machine and all other VPN Participant machines on the LAN behind the VPN Host machine will participate in the VPN.

  9. Enable the Allow client Nodes to learn of other Nodes checkbox if you wish to allow remote VPN Client Nodes that connect to the VPN Host, to learn about the other VPN Client Nodes that have connected.
  10. Click OK to return to the VPN Panel where the new hosted VPN will be listed.

Assigning permissions to join the hosted VPN

Once you have created the hosted VPN, you will need to assign permission to a WinGate VPN user(s) who will be allowed to connect to the VPN on behalf of remote Nodes. These users will be from the user database in use by WinGate on the Master Node (hosting the VPN). These credentials (user name and password) will have to be supplied in the joining configuration of any remote VPN Client Nodes that attempt to join this VPN.

Read more about setting WinGate VPN connection permissions

Exporting the host VPN configuration

When your host VPN is ready, you can export the configuration details to a vpn file(.vpn) for easy distribution to VPN Client Nodes who will be joining the VPN. The VPN Client Nodes can then import the file back into their WinGate VPN installation, so they can join the VPN.

Read more about exporting the host VPN configuration

  1. no comments yet...

Download helpfile

You can use basic Full-Text Searches against the page title and body to find matching articles. Use the following search modifiers to refine your query:

  • event management (no quotes) will find all pages containing the words "event" OR "management"
  • "event management" (with quotes) will find all pages containing the phrase "event management"
  • +event -management will find all pages containing the word "event", AND NOT the word "management"