Prtg Network Monitor Ports

[Berenice Pretlow]

PRTGrequires that several ports on your system are open and reachable for full functionality. You must make sure that specific ports are available on the PRTG web server, for remote probes, clustering, and for various monitoring technologies.

Note: If the PRTG web server always uses a fallback port after a server restart, check for programs that use the same port as PRTG on startup. For example, the integrated Microsoft IIS web server uses port 80 (443 for SSL) by default and starts before PRTG so that the port is not available for PRTG. This is why you need to define a different port for IIS or disable it. You can also disable the World Wide Web Publishing Service on startup to get the same effect.

Sensors use various monitoring technologies to query the desired data. These technologies need open ports for the communication between the PRTG core server and the monitored devices in the network. You can find a comprehensive and up-to-date list of all ports used by sensors in the PRTG Manual: List of Default Ports.

If i just open one firewall port for remote probe - 23560 (or Cluster Port set by me in the PRTG Administrator), can i use all sensors like CPU monitoring, Disk Space monitoring etc. and will i be able to monitor windows services (restart it if it's down)

We have various monitors passing over multiple firewalls monitoring different things. In the most case tcp/135 works for WMI, but we have issues when monitoring SQL and other non-standard things. When checking the firewall logs for drops we see ports (UDP & TCP) i would not be expecting from the remote probe to the end device.

Hi,

we cannot publish a complete list of used ports, because some services open high ports dynamical, so it is impossible to get a complete list. And as mentioned in my post before, the needed ports depend on the services you want to monitor and on the used protocols.

Maybe you want to install a Remote Probe as it only requires TCP Port 23560 opened for communication with the PRTG Core Server.

Best regards

I am currently trying to expose our PRTG network monitor to the web so that we can monitor the network using the PRTG app and without having to remote in to a PC on the network. I have tried to use port forwarding on our Draytek Vigor3900 firewall, which works perfectly fine when we exposed our KMV Masterview. The Masterview was already using port 443 for the SSL connection, I have set the Network Monitor to listen on port 7342.

This is the exact same setup as the other port forward, the only difference is the public port it uses, and the private port the SSL uses. I have looked up online and found that there should be no issues with changing the SSL port as long as the port forward on the firewall is trying to listen to the same private port, but when I try to open the page by going to ''it just says that the web page is not available. I also know that the network monitor is working perfectly fine when trying to access it internally.

As the firewall port forwarding rule looks good, the other important thing to check is, if the network configuration is correct. For the port forwarding to work, the PRTG server's default gateway should be the firewall. Since you have multiple WAN, so check and make sure the Server is configured with the right gateway ip.

With the PRTG Administrator program you can define various system-oriented settings that affect your PRTG installation, as well as restart services and view log information. You can change many of these settings also via the system administration in the PRTG web interface.

Note: All settings you define here are only valid for the local installation running on the computer you open the program on. In order to change settings for another installation, for example, another cluster node installation, please log in to this computer and open the program there.

Note: This section describes the available settings in the PRTG Administrator when you open the tool on the PRTG core server system (core resp. web server and local probe related). If you open this program on a remote probe machine, only probe related settings are available.

When you close the program with the Ok button after changing settings, you are asked to restart the core server Windows service and/or probe service in order to save the settings. Please confirm by clicking the OK button. Otherwise the changes are ignored.

Note: Regardless of the selected setting above, one port in the range from 8080 to 8180 has to be available on the specified IP address so PRTG can create reports. The report engine will try to connect to the core server on one of these ports.

Note: If PRTG does not find a network card on startup it will switch the IP setting to Localhost. This setting will remain, even if a network card is available later on. If you disabled or removed the network card on the machine running the PRTG core server, please re-check this setting.

You can use this, for example, to report the IP address of the current master node to a dynamic DNS provider, so a DNS name is always redirected to the current PRTG master node in case the original master node fails and a failover node (running at a different IP address) takes over the master role.

To make sure your key has been entered correctly please click on the Check Key button. A popup box will either show success or denial of your license information. License information is also checked if you change tabs.

Note: You have to use the right edition for your license key. For example, the installer for trial and Freeware edition does not accept any commercial keys. For more information, please see Enter a License Key section.

You can stop and start PRTG Windows service manually. Click the Stop Core Server resp. Stop Probe Service button to stop a service, and Start Core Server resp. Start Probe Service to start it again. Both actions usually take from a few seconds up to several minutes to complete. You can also restart the core server and probes via the PRTG web interface under Administrative Tools.

Note: If you want to schedule an automatic restart of Windows services for both core server and probe service, define a schedule on the Settings tab of a probe, section Administrative Probe Settings, in the PRTG web interface.

If you open a support ticket, Paessler support might ask you to send log files for further analysis. With the Send Logs to Paessler... button, PRTG will automatically collect, compress, and send your log files.

All PRTG Network Monitor licenses are available as subscriptions, paid annually. This way, you always have continued access to the latest version of PRTG including new features and security enhancements, as well as to our technical support.

* In PRTG, sensors are the basic monitoringelements. One sensor usually monitors one measured value in your network, forexample the traffic of a switch port, the CPU load of a server, or the free space ona disk drive. On average, you need about 5-10 sensors per device.

No, it is not possible to combine different PRTG Network Monitor licenses on one server,for example, buying a license for 500 sensors* and a license for 1,000 sensors does notmean that you can use 1,500 sensors in one installation. PRTG only accepts one licensekey per server. If you need more sensors, you can upgrade to a larger license any time.

* In PRTG, sensors are the basic monitoring elements. Onesensor usually monitors one aspect of a network device, for example the CPU load ofa server. On average, you need about 5-10 sensors per device.

Scenario 1: You want to upgrade with the start of a new subscription period. In this case, your new license contract (including the use of a larger number of sensors) is effective as of the date your new subscription period starts. Your license key remains the same.

Scenario 2: You want to upgrade mid-term. In this case, your new license contract (including the use of a larger number of sensors) is effective as of the purchase date. Please note that with the upgrade, a new subscription period starts. You will get a discount for the remaining days of the previous subscription period. Your license key remains the same.

All PRTG Network Monitor subscriptions give you continued access to the latest version of PRTG including new features and security enhancements, as well as email support via our support ticket system.

Payment by credit card: Your credit card will be charged on the day of purchase and the details securely stored. It will be charged again in the 13th and 25th months of the 3-year subscription period.

The Port Range sensor monitors a network service by connecting to various TCP/IP ports. It tries to connect to the specified TCP/IP port numbers of a device in succession and waits for each request to be accepted.

The Add Sensor dialog appears when adding a new sensor on a device manually. It only shows the setting fields that are imperative for creating the sensor. Therefore, you will not see all setting fields in this dialog. You can change all settings in the sensor's Settings tab later.

Note: Usually, a sensor connects to the IP Address or DNS Name of the parent device on which you created this sensor. See the Device Settings for details. For some sensor types, you can define the monitoring target explicitly in the sensor settings. Please see below for details on available settings.

3a8082e126