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

Remote probes are helpful for monitoring with PRTG because they can extend your monitoring.

  • With remote probes, you can monitor different subnetworks that are separated from your PRTG on premises core server by a firewall, and you can 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 systems running a remote probe.
  • You need a remote probe if you want to monitor your local network using a PRTG hosted by Paessler instance.

icon-i-roundPRTG updates remote probes automatically, but in rare cases a manual probe update is required. You receive a ToDo ticket in this case. Follow the steps below to manually update a remote probe.

icon-i-round-redIf you run PRTG in a cluster, see PRTG Cluster and Remote Probes Outside the LAN.

icon-book-arrowsIf you have issues after the installation, see section Debugging Remote Probe Connection Issues

icon-book-arrowsFor a partially automatic installation of a remote probe directly from the device tree in the PRTG web interface, see section Remote Probe Setup via Device Tools. For a quick installation guide, see the Paessler Website: How to install a PRTG remote probe in 4 steps.

Steps to Take

To install a PRTG remote probe using the Remote Probe Installer, follow these steps:

Step 1: Meet the Requirements

To install a remote probe on a computer, make sure that you meet the following requirements.

  • The target computer runs the operating system Windows 7 or later.
  • The target computer is accessible through remote procedure call (RPC). This is usually the case when your PRTG server and the target computer are located in the same LAN segment. Otherwise, open Windows services.msc on the target computer 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.
  • Connections between remote probes and the PRTG core server require port 23560. Make sure that on your PRTG core server side, this port is not blocked by firewall rules, and, on the probe side, the Transmission Control Protocol (TCP) port 23560 is open for outgoing connections as well.
    icon-book-bulbIf you need to set a different port (not recommended), see the Knowledge Base: How can I customize ports for core-probe connections used by PRTG?

icon-i-roundYour 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 PRTG core server system.

icon-book-arrowsSee also the System Requirements for PRTG Remote Probes.

Step 2: Prepare the PRTG Core Server

icon-prtg-on-demandThis only applies to PRTG on premises instances, not to PRTG hosted by Paessler.

If you use PRTG hosted by Paessler, you can start with Step 3: Download the Remote Probe Installer from the PRTG Web Interface right away.

icon-i-round-redBecause your remote probe needs to connect to your PRTG core server, PRTG needs to accept incoming remote probe connections. So, with PRTG on premises, first prepare your PRTG server before installing 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 probe settings and go to the Probe Connection Settings.

Probe Connection Settings in System Administration

Probe Connection Settings in System Administration

Step 2.1: Probe Connection IPs

By default, a PRTG core server accepts connections from the Local Probe only (IP address 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 IPs available on this computer: Any IP on your PRTG core server system accepts incoming probe connections.
  • Specify IPs: Specify selected IP addresses that accept incoming connections.

Step 2.2: Allow IPs

In the Allow IPs field, you can enter the IP address of the computer 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.

icon-i-round-redIf you use any, make sure that you only write the word in lower case. Any other variations are not 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.

icon-i-round-redIf you change this setting, PRTG needs to restart the PRTG core server to apply your changes. After clicking Save, a dialog box appears that asks you to confirm the required core server restart. Click OK to trigger the restart. During the restart, all the users of the PRTG web interface, of PRTG Desktop, or of PRTG Apps for Mobile Network Monitoring are disconnected and reconnected.

icon-i-roundTo edit the core–probe connection settings, you can also use the PRTG Administration Tool on your PRTG core server.

PRTG Cluster and Remote Probes Outside the LAN

icon-i-redIf you use the Clustering feature of PRTG and you want to run remote probes outside your local network, you have to make sure that 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 valid addresses (Domain Name System (DNS) names or IPs) 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 probe is disconnected because of this, 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 then obtains the IP address or DNS name entries that it can reach.

icon-book-arrowsSee 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 | Optional Downloads | Remote Probe Installer. Click Add Remote Probe to start the installation assistant. In the appearing dialog window, click Prepare and Download to start the download. Save the setup program to your local disk.

icon-i-roundThe Add Remote Probe button is also available in the device tree.

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

icon-prtg-on-premisesIf you connect your remote probe to a PRTG on premises instance, prepare your Probe Connection Settings first.

Add Remote Probe Assistant

Add Remote Probe Assistant

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

Step 4: Install the Remote Probe

  1. Execute the setup program that you have just downloaded.
  2. Confirm the Windows User Account Control dialog with Yes to allow the installation. The usual software installation wizard guides you through the installation process.
  3. Click Install to start the installation process of your remote probe.
PRTG Remote Probe Setup Installing

PRTG Remote Probe Setup Installing

Wait until the installation is completed. The remote probe then automatically connects to your PRTG core server.

PRTG Remote Probe Setup Connecting to Server

PRTG Remote Probe Setup Connecting to Server

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

icon-i-roundTo 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.

PRTG Remote Probe Successful Setup

PRTG Remote Probe Successful Setup

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.

Step 5: Approve the New Probe

In the installation assistant, click Installation Done.

Confirm that Installation is Done

Confirm that Installation is Done

icon-prtg-on-demandIf you successfully installed the remote probe from a PRTG hosted by Paessler installation, you see the following dialog box.

Approve PRTG Remote Probe for PRTG Hosted by Paessler

Approve PRTG Remote Probe for PRTG Hosted by Paessler

Click Approve and auto-discover to include your new remote probe device and network in your device tree and to start the 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. The probe now appears as a new object in your device tree.

For unwanted probe connections, click Cancel. A new window appears in the lower-right corner.

Deny PRTG Remote Probe

Deny PRTG Remote Probe

Click Deny to deny the new probe.

icon-i-round-redIf you deny or remove a remote probe, PRTG automatically adds this device's global ID (GID) to the Deny GIDs list in System Administration—Core & Probes. PRTG automatically denies future probe connections from this device.

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

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

icon-i-roundYou do not have to approve remote probes after updates.

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

Debugging Remote Probe Connection Issues

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

  • Recheck if you fulfilled all the requirements as described in step 1 of this section like the Windows Firewall settings.
  • 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=
11/6/2017 1:21:58 PM ssleay32.dll=
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:
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 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 because of an incorrect Access Key, or because of incorrect IP settings (see step 2), you see:

11/6/2017 1:42:02 PM Try to connect...
11/6/2017 1:42:02 PM Connected to
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 probe system.

Remote Probe Settings in PRTG Administrator

Remote Probe Settings in PRTG Administrator

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

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

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

icon-book-arrowsFor more detailed information about these settings, see section PRTG Administration Tool.


Knowledge Base: How can I customize ports for core-probe connections used by PRTG?

Paessler Website: How to connect PRTG through a firewall in 4 steps

Paessler Website: How to install a PRTG remote probe in 4 steps


Installing the Software—Topics

Keywords: Configure,Configure Probe