The RPC server is unavailable (requires acknowlegement). After has been acknowleged it does the same over and over.
Since the WMI query is most likely the trigger this RPC error, try the following checks:
On each (at least one) monitored system in question
1. Open the Command Prompt
2. cd C:\Windows\System32\wbem
3. Try “wmic path Win32_Volume”
On the Diagnostic Server machine
4. Open the Command Prompt
5. cd C:\Windows\System32\wbem
6. wmic /node:<monitored system e.g. 10.10.110.10> /user: <DOMAIN\USER> path Win32_Volume
Here’s common causes and solutions of this error.
Some are obviously not the case but No.1 (Firewall) is worth to check.
1. The remote computer is blocked by the firewall.
Solution: Open the Group Policy Object Editor snap-in (gpedit.msc) to edit the Group Policy object (GPO) that is used to manage Windows Firewall settings in your organization.
Open Computer Configuration, open Administrative Templates, open Network, open Network Connections, open Windows Firewall, and then open either Domain Profile or Standard Profile, depending on which profile you want to configure.
Enable the following exception: "Allow Remote Administration Exception" and "Allow File and Printer Sharing Exception".
2. Host name or IP address is wrong or the remote computer is shutdown.
Solution: Verify correct host name or IP address.
3. The "TCP/IP NetBIOS Helper" service isn't running.
Solution: Verify that "TCP/IP NetBIOS Helper" is running and set to auto start after restart.
4. The "Remote Procedure Call (RPC)" service is not running on the remote computer.
Solution: Verity that "Remote Procedure Call (RPC)" is running and set to auto start after restart.
5. The "Windows Management Instrumentation" service is not running on the remote computer.
Solution: Verity that "Windows Management Instrumentation" is running and set to auto start after restart.
