Previous Next

PRTG Manual: Classic Remote Probe Setup via Device Tools

You can directly install a classic remote probe via the context menu of a device in the device tree. This partially automatic installation mechanism is an alternative to the Classic Remote Probe Installer. For a quick installation guide, see the Paessler website: How to install a PRTG remote probe in 4 steps.

This is an experimental feature. It might not work in all situations. In this case, see section Debugging.

This feature is not available in PRTG Hosted Monitor.

You cannot install a remote probe on the local probe device or hosted probe device. The Classic Remote Probe Setup via Device Tools is also not available for devices on remote probes. In this case, use the Classic Remote Probe Installer.

If you run PRTG in a cluster, see Cluster and Remote Probes Outside the LAN.

Steps to Take

To install a remote probe directly from the device tree in the PRTG web interface, follow these steps:

Step 1: Meet the Requirements

To install a classic remote probe on a target system, make sure that you meet the following requirements:

The target system runs on at least Windows 10.
The target system is accessible via remote procedure call (RPC). This is usually the case when your PRTG core server and the target system are located in the same LAN segment. Otherwise, open Windows services.msc on the target system and start the RPC service.
Programs are allowed to communicate through your Windows Firewall. Open the settings of your firewall and select Allow an app through firewall. Mark the check box for Remote Service Management, and the check box Public in the corresponding line.

Because the remote probe initiates the connection, you must make sure that a connection to your PRTG core server from the outside can be established. The process is the same as if you wanted to allow access to the PRTG web server provided by the PRTG core server via port 80 or 443. In most cases, this means that you will require an allow or allow-nat network address translation (NAT) rule that enables a remote probe to reach the PRTG core server via the Transmission Control Protocol (TCP) port 23560. Then, the remote probe uses a dynamic port from the high port range (49152 - 65535) for outgoing connections.

If you need to set a different port, which we do not recommend, see the Knowledge Base: How can I customize ports for core-probe connections used by PRTG?

You cannot install a remote probe on a system that already has a probe installed.

For more information on the requirements for remote probes, see section System Requirements.

Step 2: Prepare the PRTG Core Server

Because remote probes need to connect to your PRTG core server, PRTG needs to accept incoming remote probe connections. So, with PRTG Network Monitor, first prepare your PRTG core server before you install a remote probe.

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

Probe Connection Settings in System Administration

Step 2.1: Probe Connection IP Addresses

By default, a PRTG 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 probes to connect to your PRTG core server.

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

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

Step 2.2: Allow IP Addresses

In the Allow IP Addresses field, you can enter the IP address of the target system on which you want to install a remote probe. You can also enter the word any. This sets the PRTG core server to accept remote probe connections from any IP address.

If you use any, make sure that you only write the word in lower case. Other variations are not valid.

Other settings are not required. For more information about the fields for Access Keys, Deny IP Addresses, and Deny GIDs, see section Core & Probes.

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

If you change this setting, PRTG needs to restart the PRTG core server to apply your changes. After you click Save, a dialog box appears that asks you to confirm the restart. Click OK to trigger the restart. During the restart, all users of the PRTG web interface, the PRTG app for desktop, or the PRTG Apps for Mobile Network Monitoring are disconnected and reconnected.

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

Cluster and Remote Probes Outside the LAN

If you run PRTG as a cluster and you want to run remote probes outside your local network, you must make sure that your cluster nodes and the addresses that they use are reachable from the outside. Check your cluster node settings under Cluster before you install a remote probe outside your local network. Enter valid Domain Name System (DNS) names or IP addresses for both cluster nodes to reach each other and for remote probes to individually reach all cluster nodes. 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 remote probe is disconnected because of this, follow these steps:

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

See also section Failover Cluster Configuration, section Remote Probes in a Cluster.

Step 3: Configure the Failover Node

If you have not yet done so, add a device that represents the target system on which you want to install the remote probe. Set the correct Windows credentials for this device.

Open the device settings.
In the Credentials for Windows Systems section, provide Domain or Computer Name, User Name, and Password for the target system. You can also inherit the credentials from the settings of a parent object in the device tree.

Make sure that this user account has administration rights on the target system.

Step 4: Confirm the Failover Node

In the device tree, open the context menu of the target device.
Select Device Tools | Install Remote Probe to open the install dialog in a new window.
This option is only available for devices on the local probe of PRTG Network Monitor.

Remote Probe Installation Dialog

The install dialog includes four sections:

Experimental feature notice and short introduction
Details: Overview of the device like Device Name, Status, Priority, Parent Probe, Parent Group, and Sensors by Status.
Prerequisites: Make sure that you meet the requirements listed here. If not, PRTG cannot start the installation process. Open requirements are highlighted in red.

Installation Unable to Start Because Prerequisites Are Not Met

Start Probe Installation: Time estimation for the installation and installation start button

If all prerequisites are met, you can install the remote probe on the target system by clicking Install Remote Probe on "[device name]". Wait until the process has ended. If the installation is successful, the following message appears in the Start Probe Installation section: Done. Result is: OK.

Every time you start an installation, PRTG automatically adds a new key to the field Access Keys in the Core & Probes settings, no matter if the installation is successful or not.

Step 5: Approve the New Remote Probe

If the installation is successful, you receive further instructions after the result message. You also receive a new ToDo ticket.

Click Approve and auto-discover to acknowledge the new remote probe and to instantly start an auto-discovery in this network. Click Approve new probe to acknowledge the new remote probe without running an auto-discovery. You can also discard the remote probe by clicking Deny.

When you deny or remove a remote probe, this device's global ID (GID) is listed in the Deny GIDs field in the Core & Probes settings. Future probe connections from this device are automatically denied.

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

Wait while the remote probe connects. Once the remote probe has connected, you can create groups, devices, and sensors to customize your monitoring via the new remote probe.

Debugging

Note that installing a remote probe directly from the device tree in the PRTG web interface is an experimental feature. This approach might not be possible in all situations.
Make sure you meet all the requirements as described in step 1 such as the Windows Firewall settings.
If the quick installation procedure as described in this section does not work with your setup, manually install the remote probe via the Classic Remote Probe Installer as described in section Install a Remote Probe.

KNOWLEDGE BASE