PRTG Manual: Remote Probe Setup via Device Tools
Directly install a remote probe by right-clicking a device in the PRTG device tree. This partially automatic installation mechanism is an alternative to installing a remote probe using the 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 may not work in all situations. In this case, see section Debugging.
This feature is not available in PRTG hosted by Paessler.
You cannot install a remote probe on the local probe or hosted probe device. The Remote Probe Setup via Device Tools is also not available for devices on remote probes. In this case, use the Remote Probe Installer.
If you run PRTG in a cluster, see PRTG Cluster and Remote Probes Outside the LAN.
Steps to Take
To install a PRTG remote probe directly from the device tree in the PRTG web interface, follow these steps:
- Step 1: Meet the Requirements
- Step 2: Prepare the PRTG Core Server
- Step 3: Provide Credentials (Optional)
- Step 4: Install the Remote Probe
- Step 5: Approve the New Remote Probe
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.
If 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?
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.
See also the System Requirements for PRTG Remote Probes.
Because 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.
Step 2.1: Probe Connection IPs
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 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.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.
If 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.
If you change this setting, PRTG needs to restart the 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.
To edit the core–probe connection settings, you can also use the PRTG Administration Tool on your PRTG core server.
If 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:
- Uninstall the current remote probe.
- Update the cluster node settings with addresses that are reachable from outside your LAN.
- Restart your 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—Remote Probes in Cluster.
If you have not yet done so, add a device to PRTG that represents the target computer 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, and Password for the target computer. 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 computer.
- In the device tree overview, 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 PRTG on premises local probe.
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 State.
- Prerequisites: Make sure that you meet the requirements listed here. If not, PRTG cannot start the installation process. Open requirements are highlighted in red.
- 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 computer by clicking the button 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 System Administration—Core & Probes, no matter if the installation has been successful or not.
If the installation is successful, you receive further instructions after the result message. As indicated, go back to the device tree and acknowledge the new probe. The approval button appears under the node of the new remote probe. You also receive a new ToDo ticket.
Click Approve and auto-discover new probe to acknowledge the created remote probe and instantly start an Auto-Discovery in this network. Click Approve new probe to acknowledge the remote probe without running an auto-discovery. You can also discard the probe by clicking Deny new probe.
When you deny or remove a remote probe, this device's global ID (GID) is listed in the Deny GIDs field in System Administration—Core & Probes. Future probe connections from this device are automatically denied.
Denying 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.
After approving, the approval button changes to a Working status. Wait while the probe is connecting. Once the probe has connected, you can create groups, devices and sensors to customize your monitoring via the new probe.
- Note that installing a remote probe directly from the device tree in the PRTG web interface is an experimental feature. This approach may not be possible in all situations.
- Recheck if you fulfilled all the requirements as described in step 1 of this section like the Windows Firewall settings.
- If the quick installation procedure described in this section does not work with your setup, manually install your remote probes via the Remote Probe Installer as described in section Install a PRTG Remote Probe.
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
- Active Directory Integration
- Application Programming Interface (API) Definition
- Filter Rules for xFlow, IPFIX, and Packet Sniffer Sensors
- Channel Definitions for xFlow, IPFIX, and Packet Sniffer Sensors
- Define IP Ranges
- Define Lookups
- Regular Expressions
- Calculating Percentiles
- Add Remote Probe
- Failover Cluster Configuration
- Data Storage
- PRTG Housekeeping
- Using Your Own SSL Certificate