All Collections
Troubleshooting and How-To
How-To Articles
How to access Teramind server outside the local network
How to access Teramind server outside the local network
A
Written by Arick Disilva
Updated over a week ago

There are two ways you can enable users to login to your Teramind Dashboard from outside the local network:

Configure a VPN (recommended option)

You can set up a VPN so that employees can connect to the corporate network from the public internet. This provides some advantages such as more security (VPN communications usually are encrypted) and, unlike the method below, you do not need to redeploy the current agents.

Make the server public

You can expose your Teramind server to the internet so that it can be reached from anywhere. You can do this by assigning a public IP address and a valid domain name to the server.

To enable agents to connect to the Teramind server both inside and outside the corporate network without using a VPN connection, create rules on the firewall and a public FQDN (fully qualified domain name). You can also add DNS records to your internal and public DNS configuration so that the public FQDN (ex: teramind.corporatedomain.com) can be resolved by monitored computers to the Teramind server's IP both inside and outside the corporate network.

For firewall rules, please refer to the following KB articles for more details on the ports needed for agents to connect to the Teramind server:

To allow the web dashboard to be accessible outside the corporate network, it is recommended to set a public hostname in the Teramind web dashboard and upload a trusted SSL certificate. Please refer to the following sections of our User Guide for more information:

Note that, you will need to redeploy the currently installed agents or they will not be able to connect to the new IP address/hostname.

If you’re changing agents to connect to a new hostname from a previous hostname then you may be able to edit your DNS records to point the new hostname to the existing Teramind server IP and then agents should be able to connect to the new server hostname without having to reinstall the agents.

Another option to reconfigure agents to connect to a new server IP or hostname without reinstalling the agents is to edit the agent’s configuration file. However, this configuration file has to be edited on each monitored computer so uninstalling and reinstalling the agent is often an easier approach.

If you would like to edit the agent’s configuration file to redirect it to a new server IP or hostname, the steps have been provided here:

Did this answer your question?