<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Install a PRTG Remote Probe

Why are remote probes helpful for monitoring with PRTG? Because you can extend your monitoring.

• Remote probes allow you to monitor different sub-networks that are separated by a firewall from your PRTG on premises core server and to keep an eye on remote locations. You can install one or more remote probes.
• Remote probes are useful if you want to distribute monitoring load by taking it from the system running the PRTG core server and putting it on one or more remote probe machines.
• You will need a remote probe if you want to monitor your local network using a PRTG hosted by Paessler instance.
• Remote probes may be suitable monitoring components in several individual scenarios that depend on your custom network setup.

All you need is a computer on which you can install your remote probe. See also the System Requirements for PRTG Remote Probes.

Steps to Go

To install a PRTG Remote Probe, follow these steps:

1. Prepare the PRTG Core Server: only required for PRTG on premises

2. Download the Remote Probe Installer: start here if you use PRTG hosted by Paessler

3. Install the Remote Probe

4. Approve New Probe and Start Monitoring

Your PRTG on premises or PRTG hosted by Paessler installations already include a local probe or hosted probe on the PRTG core server. This is why you cannot additionally install a remote probe on your core server system.

PRTG updates remote probes automatically, but in rare cases a manual probe update is required. You will receive a ToDo ticket in this case. Please follow the steps below to manually update a remote probe.

If you have issues after the installation, see this section: Debugging Remote Probe Connection Problems

Do you run PRTG in a cluster? Then mind this important note.

---

1. Prepare the PRTG Core Server

Because your remote probe needs to connect to your PRTG core server, PRTG needs to accept incoming remote probe connections. So, on PRTG on premises, prepare your PRTG server first when want you install the remote probe.

Edit the relevant settings in System Administration—Core & Probes. From the main menu in the PRTG web interface, select Setup | System Administration | Core & Probes to access the probes settings and go to the Probe Connection Settings.

Step 1: Probe Connection IPs

By default, a core server accepts connections from the Local Probe only (IP address 127.0.0.1). This setting is the most secure setting, but it does not allow any remote probe to connect to your PRTG core server.

To accept remote probes, choose one of the following settings:

• All IPs available on this computer: Any IP on your core server system accepts incoming probe connections.
• Specify IPs: Specify selected IP addresses that accept incoming connections.

Step 2: Allow IPs

In the Allow IPs field, you can enter the IP address of the computer you want to install a remote probe on. To make things easier, you can also enter the word any. Any will set the PRTG core server to accept remote probes connecting from any IP address.

If you use any, make sure you write the word in lower case only! Any other variations will not be valid!

Changing other settings is not required. For details about the fields for Access Keys, Deny IPs, and Deny GIDs, see section System Administration—Core & Probes.

When you are done, click Save to save your settings.

If you change this setting, PRTG needs to restart the core server to apply your changes. After clicking the Save button, a dialog box appears that asks you to confirm the required core server restart. Click OK to trigger the restart and follow the instructions on the screen. During the restart, all the users of the PRTG web interface, of the Enterprise Console, or of PRTG Apps for Mobile Network Monitoring will be disconnected and reconnected.

To edit the core–probe connection settings, you can also use the PRTG Administration Tool on your core server.

PRTG Cluster and Remote Probes Outside the LAN

If you use the Clustering feature of PRTG and you want to run remote probes outside your local network, you have to make sure your cluster nodes and the addresses they use are reachable from the outside! Check your cluster node settings under System Administration—Cluster before installing a remote probe outside your local network. Enter addresses (DNS names or IPs) that are valid for both cluster nodes to reach each other and for remote probes to reach all cluster nodes individually. Remote probes outside your LAN cannot connect to your cluster nodes if they use local addresses.

If you already have a remote probe installed outside your LAN and the probe is disconnected because of this, please follow these steps:

1. Uninstall the current remote probe.
2. Update the cluster node settings with addresses that are reachable from outside your LAN.
3. Restart your PRTG core servers.
4. Install the remote probe again. It will then obtain the IP address or DNS name entries that it can reach.  

See also section Failover Cluster Configuration—Remote Probes in Cluster.

---

2. Download the Remote Probe Installer from the PRTG Web Interface

On the computer on which you want to install a remote probe, log in to the PRTG web interface. From the main menu bar, select Setup | Downloads and Tools | Remote Probe Installer. Click Add Remote Probe to start the installation assistant. In the appearing dialog window, click Prepare and Install to start the download. Save the setup program to your local disk.

The Add Remote Probe button is also available in the device tree.

Using the installation approach with the assistant, PRTG will guide you through the install process. If you Download the Remote Probe Installer directly, you have to install the remote probe without the assistant.

If you connect your remote probe to a PRTG on premises instance, prepare your Probe Connection Settings first.

The version numbers of core and probe services must match. PRTG updates probes automatically when a new version is installed on the PRTG core server. If PRTG advises you to update your remote probe manually, open a web browser on your remote computer and download the remote probe installer as described in this manual section.

The PRTG core system already includes a local probe or hosted probe service. This is why you cannot additionally install a remote probe on that system.

3. Install the Remote Probe

• Execute the setup program that you have just downloaded.
• Confirm the Windows User Account Control dialog with Yes to allow the installation. The usual software installation wizard will guide you through the installation process.
• Click Install to start the installation process of your remote probe.

Please wait until the installation is completed. The remote probe will automatically connect to your PRTG core server.

If the remote probe successfully connects to your PRTG core server, you can complete the setup of your new remote probe.

To allow your new remote probe to connect to a PRTG hosted by Paessler instance, PRTG automatically sets the Allow IPs field in System Administration—Core & Probes to any. You can also use any for PRTG on premises, but we recommend that you use this setting in intranets only. If any is not an option for you, cancel it in the Allow IPs field and enter the IP address of your remote probe instead.

Click Continue to finish the remote probe installation.

Finally, click Finish to exit the installation wizard. The remote probe is now installed on your computer as a Windows service.

Approve the New Probe and Start Monitoring

Remember to log in to the PRTG web interface, confirm that the installation is done, and acknowledge your new remote probe!

In the installation assistant, click Installation Done.

If you successfully installed the remote probe from a PRTG hosted by Paessler installation, you will see the following dialog box.

Click Approve and auto-discover new probe to include your new remote probe device and network in your device tree and to start the PRTG auto-discovery. It helps you discover devices and automatically create suitable sensors. Optionally, you can also choose to only approve your remote probe without starting an auto-discovery by clicking Approve new probe. The probe now appears as a new object in your device tree.

For unwanted probe connections, you can click Deny new probe. Note that this does not uninstall the remote probe, but only prohibits the probe from connecting to the PRTG core server.

If you deny or remove a remote probe, PRTG will automatically add this device's global ID (GID) to the Deny GIDs list in System Administration—Core & Probes. Future probe connections from this device will be denied automatically.

Denying the remote probe in the PRTG device tree does not uninstall the probe, but only denies access to the core server. The probe will continue to run on the target system until you uninstall it manually.

In the Approving probe dialog, click OK to exit the dialog, or click Show probe in device tree to open the new probe in the device tree directly.

Once approved, PRTG automatically creates a set of sensors for the probe to ensure you can detect bottle-necks on the probe system immediately. We recommend that you keep these sensors. You can now create groups, devices, and sensors for monitoring via the new probe.

You do not have to approve remote probes after updates.

When a new probe connects to the core server for the first time, you will receive a new ToDo ticket in the PRTG ticket system.

---

Debugging Remote Probe Connection Problems

If you have trouble with your core probe connection, make sure that you meet the following requirements:

• The IP address of the computer on which you want to install a remote probe is not listed in the Deny IPs field in System Administration—Core & Probes.
• On your PRTG core server side, the default port 23560 for probe connections is not blocked by firewall rules, and, on the probe side, the TCP port 23560 is open for outgoing connections as well.

If you need to set a different port (not recommended), see this Knowledge Base article: How can I customize PRTG's ports for core-probe-connections?

• You can also take a look at the probe's logfiles. The probe process writes logfiles with a file name in the format PRTG Probe Log (x).log. Open the one with the most recent date.

For a correct connection the probe log should look similar to this:

11/6/2017 1:21:58 PM PRTG Probe V17.4.36.3253
11/6/2017 1:21:58 PM System time zone: (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna
11/6/2017 1:21:58 PM libeay32.dll=1.0.2.11
11/6/2017 1:21:58 PM ssleay32.dll=1.0.2.11
11/6/2017 1:21:58 PM PRTG Probe "example-DNS" starting on "example-DNS" (GID={AAAA1111-22BB-33CC-DD44-EEEEEE555555})
11/6/2017 1:21:58 PM Memory Manager: NexusMM4
11/6/2017 1:21:58 PM OS: Microsoft Windows 10 Enterprise (10.0 Build 15063), 4 CPUs (Quad x64 Model 78 Step 3), code page "Windows-1252", on "NVME SAMSUNG MZFLV256"
11/6/2017 1:21:58 PM Data Path: C:\ProgramData\Paessler\PRTG Network Monitor\
11/6/2017 1:21:58 PM System Path: C:\Program Files (x86)\PRTG Network Monitor\
11/6/2017 1:21:58 PM Local IP: 0.0.0.0
11/6/2017 1:21:58 PM Core Server IP: example-DNS.exampledomain.com
11/6/2017 1:21:58 PM Core Server Port: 23560
11/6/2017 1:21:58 PM SSL Enabled
11/6/2017 1:21:58 PM Probe GID: {AAAA1111-22BB-33CC-DD44-EEEEEE555555}
[...]
11/6/2017 1:21:58 PM Start Connection
11/6/2017 1:21:58 PM Start Done
11/6/2017 1:21:58 PM (14608):Initializing WMIConnectionPool
11/6/2017 1:21:58 PM (14608):WMIConnectionPool maximum number of concurrrent establishings is set to: 20
11/6/2017 1:22:03 PM Connect from  to example-DNS.exampledomain.com:23560
11/6/2017 1:22:03 PM TCP connected from 10.49.12.51:55199 to example-DNS.exampledomain.com:23560
11/6/2017 1:22:03 PM State changed to connected (example-DNS.exampledomain.com:23560)
11/6/2017 1:22:03 PM Reconnect
11/6/2017 1:22:04 PM Connected
11/6/2017 1:22:10 PM Send Login
11/6/2017 1:22:10 PM Local: 11/6/2017 1:22:10 PM UTC: 11/6/2017 12:22:10 PM
11/6/2017 1:22:10 PM MarkUnused
11/6/2017 1:22:10 PM Login OK: Welcome to PRTG

If the connection fails, for example due to an incorrect Access Key, or due to incorrect IP settings (see Prepare the PRTG Core Server), you will see:

11/6/2017 1:42:02 PM Try to connect...
11/6/2017 1:42:02 PM Connected to 10.0.2.167:23560
11/6/2017 1:42:07 PM Login NOT OK: Access key not correct!

 

If you need to adjust any probe settings for the connection to the PRTG core server, use the PRTG Administration Tool on your remote probe system.

In the Connection to PRTG Core Server tab, you can then edit the following settings:

• Server: Enter the IP address or DNS name of the core server the remote probe will connect to. If Network Address Translation (NAT) is used, this has to be the IP address that is externally visible, because the remote probe will connect from outside your network.
• Probe Access Key and Confirm Access Key: Enter the access key that the probe will send to the core server. This access key has to be defined on the PRTG core server in System Administration—Core & Probes. Make sure the key phrases match exactly.

Remember to always click Save & Close to confirm your settings and to (re)start the probe service.

For more detailed information about these settings, see section PRTG Administration Tool.

More

Knowledge Base: How can I customize PRTG's ports for core-probe-connections?

• https://kb.paessler.com/en/topic/65084

 

Installing the Software—Topics

• Download PRTG
• Update From Previous Versions
• Install a PRTG Core Server
• Create a PRTG Hosted by Paessler Instance
• Install a PRTG Cluster
• Enter a License Key
• Activate the Product
• Install a PRTG Remote Probe
• Install the Enterprise Console
• Uninstall PRTG Products