The issue
There happens a situation where one wants to collect performance counters about a server from a remote server within the same domain. However trying to access the server fails with the error that performance counters for the server aren’t accessible.
This could also happen even when the “Performance logs and alerts” service is running.
The cause
This issue is caused by the firewall blocking remote procedural calls to enable sending back and forth performance data.
The remedy
It can be solved by opening up TCP port 445. Create both inbound and outbound rules.
Caution
The rules created should only apply to the Domain network and not public networks.