Hi all,
- Setup PortState as Custom EXE/Script
- Select PortState.exe
- Entered the parameters:
-id=%sensorid -h=%host -p=34780 -pt=UDP
Once created, PRTG created 3 channels/status:
| Channel ID | Last Value | |
|---|---|---|
| Downtime | -4 | |
| Execution Time | 1 | 2,135 |
| Value | 2 | 4,270 |
From the channel, how do I know if the port is down?
Article Comments
Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.
Hi Sebastian,
PortState can be download from PRTGToolsFamily.com website (https://prtgtoolsfamily.com/downloads/download/565e76af-60d0-428b-8e7f-e79015a1e295).
Feb, 2021 - Permalink
Hi,
If the port can not be monitored properly the sensor will show an error message:
| The external .exe file or script has not returned a response. (code: PE087) |
Please find the developers regarding this custom sensor on our knowledge base here.
If you just want to figure out whether a port is closed or open, you can also check the native Port Sensor that comes with each PRTG installation.
Best,
Sebastian
Feb, 2021 - Permalink
Hi there,
where is PortState coming from? What resource does you use as it appears to be no native sensor.
My gut feeling would be if the port is closed, the script returns an error and so is the sensor. But as it is a custom one I can't tell that for certain.
Best,
Sebastian
Feb, 2021 - Permalink