WMI Error returned from wrong port
Modified on 2025-06-10 11:46:24 +0200
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.
Important: We no longer maintain this article. The information might be out of date.
I've configured my servers to be listening on WMIFixedport 135.
When I created the device and sensors, the WMI error (Port Error 49154: RPC Server not acessible)
But I tested that Port 135 is open on the firewall and I could telnet to it.
Is this a PRTG bug???
Article Comments
Hello,
can you scan against the target with our WMI Tester on this port?
best regards.
Aug, 2011 - Permalink
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.
Hello,
can you scan against the target with our WMI Tester on this port?
best regards.
Aug, 2011 - Permalink