Sometimes ping stops working for a som probes. We can litterately not ping the address from that PRTG machine. A server reboot fixes the problem or a tracert to the address.
Windows 2008 R2 Standard 64bit
PRTG: V8.2.1.1931
Feels like this is OS related though.
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.
Hello,
PRTG uses the icmp.dll from Windows, and it's not really clear to us where this one should stumble and then work again after the use of tracert.
If this only effects certain targets, you might want to rather take a closer look at those, respectively the 'hops' in between. Maybe it's the routing (and then tracert updates the routes on the PRTG host), but that's just guess-work I'm afraid (wireshark might help here). A few more tipps:
- Which targets are effected?
- What do they have in common (networking hardware, subnets, etc.)?
- Which infrastructure lies in the way from PRTG to the targets?
best regards.
May, 2011 - Permalink
Hello,
PRTG uses the icmp.dll from Windows, and it's not really clear to us where this one should stumble and then work again after the use of tracert.
If this only effects certain targets, you might want to rather take a closer look at those, respectively the 'hops' in between. Maybe it's the routing (and then tracert updates the routes on the PRTG host), but that's just guess-work I'm afraid (wireshark might help here). A few more tipps:
best regards.
May, 2011 - Permalink