Hello,
Guided by the answer on the following page: https://helpdesk.paessler.com/en/support/solutions/articles/76000062954-my-wmi-sensors-don-t-work-what-can-i-do
I tried to setup a WMI connection on PRTG.
steps taken:
1) windows firewall is not activated on probe and target
2) DCOM enabled on probe and target
3) administrator user used
4) port 135 opened and range 49152-49252 opened
5) range defined in connect-oriented TCP/IP menu
6) RPC service running
The setup we have is that all ports need to be whitelisted, are there any ports missing that are needed for the setup? At this moment only ping shows up when an auto-discover is run.
Article Comments
Dear Erhard,
Thanks for the fast reply!
The WMI tester gives in certain cases (OS & Processes) feedback back but with adding a manual check you receive a timeout. Also the WMI tester does not give feedback on the last four advanced checks.
Pieter
Dec, 2018 - Permalink
Hi Pieter,
Please send us logs using "Setup | Contact Support" in PRTG, then we'll see form there what we can do. Mention this thread when you open the ticket, it will be addressed to me then to further work on it.
Kind regards,
Erhard
Dec, 2018 - Permalink
Hi
What was the solution of this problem?
Because I have the same issue.
Best,
Marjolein
Nov, 2019 - Permalink
Hi there,
It has to be investigated individually, as there are several things that could lead to this, therefor please open a ticket using "Setup | Contact Support" in PRTG.
Kind regards,
Erhard
Nov, 2019 - Permalink
Hello there,
What happens when you try to add a WMI Free Disk sensor manually to the device in PRTG for example? Sometimes it can make a huge difference whether you query the device by ip or its hostname/fqdn, try all variants.
Also try with our WMI Tester. On this page you find a few examples of the queries from some of the WMI sensors. On tab "Advanced" in WMI Tester when selecting option "Custom" you can run those particular queries then.
Kind regards,
Erhard
Dec, 2018 - Permalink