What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Connection could not be established

Votes:

0

I am getting this superfluous message on a free disk space sensor - it would be better not to get the message at all. Some of these messages also go on to say:

Call was canceled by the message filter

What does this mean?

message message-filter sensor

Created on Feb 28, 2012 4:54:22 PM



2 Replies

Votes:

0

Hello,

"Call was cancelled by the message filter" is an error which does not come from PRTG. This comes directly from the monitored machine. We know from other customers with this error, that they needed to reboot the monitored machine to 'fix' this error.

best regards.

Created on Feb 29, 2012 3:10:39 PM by  Torsten Lindner [Paessler Support]



Votes:

0

I came across this and an upgrade of PRTG as well as restarts of the probe/device didn't fix it. The frustrating thing was it was only some WMI sensors on some hosts, not all WMI sensors on some hosts, etc.

The hosts were all monitored by IP address but changing to hostname/FQDN seemed to fix it. It'd be time-consuming to update all the hostnames without a PowerShell (or similar) API (hint hint Paessler ;-)) so fixing it by changing all devices to hostname would be time consuming.

I found that a quick:

> ipconfig /flushdns (not sure if that's required but it was thrown in for good measure)
> ipconfig /registerdns

from an administrative command prompt on the device that was giving the error fixed the issue. It doesn't contribute to root cause but is a quick solution to the problem.

Update: The error occurred again shortly after the above steps were completed. The cause may have been traced to an Active Directory design issue. Fixing up AD Sites and Services so that servers correctly communicated with the most appropriate Domain Controller seemed to rectify the issue or has done so far.

Created on Jan 11, 2016 10:20:16 PM

Last change on Jan 18, 2016 8:39:27 AM by  Torsten Lindner [Paessler Support]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.