Implementation

Goverlan Reach Gateway Services are enabled via the Goverlan Reach Server (GRS). The Goverlan Reach Server is a software component that can be installed on Windows Server 2008 or later.

Implementing a Goverlan Reach infrastructure is done via the following 3 steps:

Basic Configuration

This configuration applies to corporate infrastructures and to software product vendors who want to support their products via On-Demand support sessions.

At least ONE Primary GRS must be installed on the private network where the Goverlan support operators are located.

This configuration allows for unattended access of any client computer equipped with the Goverlan Reach Client Agent as well as attended access of any other computer via an On-Demand Reach session.

This configuration is defined under Implementing the Master GRS.

Adding Support for Remote Client Sites

A Client Site configuration applies to IT Service Providers who wish to manage their customer sites with Goverlan Reach Gateway Services. Client Sites can also be used by multi-site enterprise environments to extend Reach Services to them.

In order to manage entire client sites remotely without a VPN connection, an additional Secondary GRS needs to be implemented at each client site:

This configuration is defined under Enabling Remote Client Sites with Reach.

 

Implementing the Master GRS

GRS Configuration Steps

Download and Install the GRS

The latest Goverlan Reach Server can be downloaded by logging into my.goverlan.com, selecting the Goverlan Reach Server tab and clicking on Download Product.

Minimum System Requirements: The Goverlan Reach Server software can be installed on any Windows Server 2008/Server 2008 R2 or later operating system with a minimum of 4GB of RAM and 200MB of available disk space. ​

Configure the Goverlan Reach Server

Open the Server Configuration window and configure the following options:

Relationship

A GRS can be a primary server or a dependent server. The primary server is installed within the authoritative site (the site where Goverlan Operators reside). In the case of a MSP implementation, client-site GRS’s will be dependent on the primary (covered later under Enabling Remote Client Sites with Reach).

For this master server, keep this setting as the Primary Goverlan Reach Server.

Server Settings

Network Configuration

The port exposed on the internal side of the network used to provide GRS services to your internal machines is defined here. This port should be reachable by all of your machines within the private infrastructure.

The default port number is 22100.

Server Services Authentication

Enter the user ID and password that will be used to start the Goverlan Reach Server and Goverlan Reach Gateway Services.

This account needs to have the following privileges:

  • Logon as a service permission
  • Local Administrator permission on the server
  • DB Creator right if using a MS SQL Server (Optional)

http://assets.goverlan.com/userguide_img/images/Service%20Account.png

Database Settings

By default, the GRS installer will automatically install a LocalDB database. This file-based database can accommodate medium sized networks of up to 500 nodes. No further configuration is necessary for the LocalDB database.

For larger networks, use the GRS settings to switch to a MS SQL Server/Express instance for the database.

SQL Server Configuration

Change the database type to Microsoft SQL Server and enter the SQL Server details. The Service Account configured in Service Account Configuration is used when Windows Authentication is selected.

If SQL Authentication is required, change the authentication method and enter the SQL account credentials.

http://assets.goverlan.com/userguide_img/images/reach%20db%20configuration.png

Reach Gateway Configuration Steps

The Goverlan Reach Gateway Service requires two TCP ports to be configured. One which is facing the inside of your network, and one that is exposed to the internet through your firewall.

The external TCP port will be used to communicate with external endpoints. Configure your external firewall with a PAT (Port Address Translation) or a NAT (Network Address Translation) rule that is directed at the Goverlan Reach Server’s IP and configured external TCP port.

It is recommended that a friendly DNS name be assigned to the public IP address.

For Example: reach.corpxyz.com would point to the external IP address of the firewall where the rule is configured.

Please refer to your router’s documentation for specific information regarding port forwarding.

Note

Make sure that the Windows firewall allows all of the configured TCP ports used by the GRS and Reach.

http://assets.goverlan.com/userguide_img/images/Reach%20Network%20Config.png

Automatically publish these settings to all Operators

This option controls the way the Reach configuration is pushed to all of your machines within your infrastructure and should be turned ON in most cases. Do not disable this option unless you have implemented a dedicated GRS server and a separate Reach server.

Name of this Organization

Enter the name of your organization in this field (for instance ‘Corp XYZ, Inc.’). This name will be used during On-Demand Support Sessions to brand the package for the remote client. It will also be used as the default Reach container for corporate clients that are connected from outside of your private network.

Public Facing Reach Address

Enter the Public DNS Name (or IP address if no DNS name has been configured) exposed to the public facing side of your network, as well as the port number to be used for communication.

Secure with Certificate

In the event that a DNS name is configured, you can associate a public certificate with it. Associating a public certificate will further secure the network connection between your clients to your Reach server by enforcing a TLS handshake.

It is strongly encouraged to associate an identity certificate to your Reach public facing address. See: Reach Security.

Private Facing Reach Address

Enter the FQDN or IP address of the local server, as well as the port number to be used for communication. This address will be used by Goverlan Operators within your network to communicate with the Reach Server.

Note

For security reasons, Goverlan Operators can only use Reach Services when connected on the same network as the Private Facing Reach Address.

Goverlan Reach Repository

The Goverlan Reach Repository holds active Reach node registration records and is used to browse through the available external endpoints.

The Remove Stale Computer Records setting defines the number of days to wait before removing stale Reach node records. If an external endpoint has not communicated with the Reach server for the configured period, it is automatically removed from the repository.

You can also view and remove stale registrations from the Goverlan Reach Server. Click on View Nodes in the ribbon bar, select Show Registered but disconnected nodes, select the disconnected registrations you wish to delete and click the Delete Records button. Or choose the Clean Records older than XX days option.

This section is irrelevant for On-Demand Only Reach implementations

 

Advertising the Goverlan Reach Server

To consume GRS services, the implemented GRS must advertise its existence on your network. The GRS advertisement enforces that the configured policies and Reach configuration is applied across all Goverlan software within your infrastructure (both Operator and Client side).

The GRS existence can be published using one of the following methods:

Please refer to the GRS User Guide Instruction page explaining these methods.

Start Your Engines

Once you have configured the GRS/REACH server, you are ready to start the services.

  • Click on the Server Controls tab and click on Start.
  • Click on the Goverlan REACH tab and click on Start the Server.

 

Was this article helpful?

Related Articles