Ping Sensor always shows 0 milliseconds

Hello,

thank you very much for your KB-Post. May I ask, could you please upload a few screenshot showing us these discrepancies?

best regards.

The screenshot shows the 0msec response time that PRTG is reporting for google.com on the left side and a ping to the same on the right displaying 6-8msec response time.

With Ping sensors PRTG actually does not measure the response time itself. It uses the Windows API and then uses the returned value from the Windows API call. That should have the same precision as the ping from commandline. Do you get any other/higher response times on any other Ping sensors? What are the exact settings for this Ping sensor?

I receive the same 0 msec response time for all of the ping sensors.

Sensor Name : google.com Timeout : 5 Packet Size : 32 Ping Count : 10 Ping Delay : 5

These settings are absolutely fine. We honestly can't really explain this, you should of course see other response times than 0 there on different ping sensors. Is this a virtual machine running PRTG here?

This is a virtual machine on VMWare ESXi 5.1 I will be reinstalling PRTG on this system and seeing if something was corrupted during the original install.

Could you possibly also try a Remote Probe on a physical machine please? And then run some Ping Sensors underneath this Remote Probe.

I uninstalled and reinstalled PRTG. Even after deleting the PRTG related program files sub-folder, all settings from the previous install were intact after the reinstall. I did perform a reboot between uninstalling and reinstalling.

I have installed the remote probe on my laptop and have created the ping sensors under this probe. I briefly got realistic ping times in the output, but all ping sensors have since returned to 0 msec.

Is there a way to completely eradicate all settings for PRTG after uninstalling through the windows GUI?

You could stop the PRTG Services, and then clear the PRTG Data Folder. Upon restarting the PRTG Core Service, a new empty default configuration will be added again.

Can you confirm that you are pinging from the local probe and not the remote probe? if the ping sensor is on a device under the remote probe, then it's likely that the ping test is between the remote probe and the remote device, i.e. well below 1ms (which should then show 0ms). By duplicating the check to the probe and not the sensor, you may have more chance of getting what you want. Also check out the QoS sensor to measure health between probes (see https://kb.paessler.com/en/topic/24053-can-a-remote-probe-ping-other-devices#reply-71763).

Thomas