Has anyone using PRTG been able to get average results for the packet loss channel on a PING sensor?
I have been trying to use a SENSORSXML from PRTG Tools Family. I am using the the SensorAverageXML custom sensor, under the EXE/Script Advanced, the parameter I am using are the followings:
-pu=mydomain\david -pp=PASSWORD -ps=192.168.1.1:8080 -s=4512 [-m=5]
Parameters Template:
| -pu=domain\username -pp=password -ps=server -s=sensorID [-m=minutes] |
The error will output: "Unable to connect to the remote server" ???
Are the other ways to average the packet loss values to 5 minutes? The plan is to get an email alert when the Packet Loss channel in a PING sensor hits more than 5%.
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.
I have removed the domain name as well. I was using the credentials to the server but didn't work. I also used the PRTG admin username and password and still get the error "<prtg><error>1</error><text>The remote server returned an error: (401) Unauthorized.</text></prtg>" and "Unable to connect to the remote server" ???
May, 2016 - Permalink
Are you 100% sure that the password is correct? Can you try an administrative account with a rather simple password and check it again?
May, 2016 - Permalink
I tried the PRTG administrative web login password, and I still get the error: "Unable to connect to the remote server"
I also tried the PRTG server login admin password and get the same error.
May, 2016 - Permalink
I am positive the credentials are correct. Maybe some step-by-step info on how to setup the SensorAverageXML would be great? I am note sure what i am doing wrong if is the credentials or the way the probes need to be setup.
May, 2016 - Permalink
Argh it just hit me ... are you really using [-m=5] in the parameters? Please discard it :) On the other hand, the output of the sensor is always 0, no matter what sensor I use. It may or may not work correctly with current PRTG versions after all.
May, 2016 - Permalink
So you are saying only use:
| -pu=mydomain\david -pp=PASSWORD -ps=192.168.1.1:8080 -s=4512 |
Remove the [-m=minutes]. What/Where should I set the amount of minute to average the packet lost ?
Jun, 2016 - Permalink
Sorry, I put this wrong - I meant if you're literally using [-m=5] instead of -m=5? :)
Jun, 2016 - Permalink
okay! so this is what I am trying these parameters now:
.\SensorAverageXML.exe -pu='prtgadminuser' -pp='317231298' -ps='https://prtg.mydomain.com/' -s=9234 -m=5
I am testing it with web PRTG admin credentials and its passhash (these are not actual credentials, but similar concept).
I get the error message that outputs will say: <prtg><error>1</error><text>No channels in XML result</text></prtg>
Any thoughts???
Jul, 2016 - Permalink
You might want to drop support@prtgtoolsfamily.com a mail :) Feel free to share the actual solution :)
Jul, 2016 - Permalink
Alright Thanks! I will definitely post the solution! Been working with PRTG for almost 2 years now. I enjoy this network monitor software.
Jul, 2016 - Permalink
We found the solution. The best advice is create a read only user (similar to SNMP community users) and then follow this page to correctly transmitted to my script : https://helpdesk.paessler.com/en/support/solutions/articles/76000063264-how-can-i-test-if-parameters-are-correctly-transmitted-to-my-script-when-using-an-exe-script-sensor
For example:
-pu='prtgadminuser' -pp='317231298' -ps='https://prtg.mydomain.com/' -s=9234 -m=10
Also try to use the try the passhashtool and generate a hash password instead of having the plain text password broadcast. http://prtgtoolsfamily.com/us/products/tools/passhashtool
Aug, 2016 - Permalink
Usually, PRTG usernames don't have the domain name in them. Can you leave it out (the backslash as well) - can you check if it works then?
May, 2016 - Permalink