Perfmon – "The parameter is incorrect." error when trying to connect to another computer-Collection of common programming errors

I’m hoping someone has run into this before and may be able to shed some light on this issue.  In a test environment, we need to be able to connect from one computer to another in perfmon.

 Issue:

On “”..

Open perfmon.exe > right-click on “Performance” > select “Connect to another computer.” > enter the name of “”  > get the following error.

############################################

Window Title: Performance Monitor

Error:  When attempting to connect to the remote computer the following system error occurred:

The parameter is incorrect.

############################################

Note:  I am using just two servers to test this, but this behavior occurs on all servers in the domain.

 Environment:

Server 2008 R2

Single domain

Firewalls disabled through GPO

Performance Logs and Alerts exception created in firewall via GPO

 Troubleshooting tests done so far:

-Verified open network communication.

-Verified DNS functioning properly.

-Turned on Network Discovery.

-My domain account is a member of domain admins and explicitly configured as local admin on both servers.

-My account, domain users, and the AD machine object for the opposite server are all in the “Event Log Readers”, “Performance Log Users”, and “Performance Monitor Users” groups on both servers.

-“Remote Registry”, “Performance Counter DLL Host”, and “Performance Logs & Alerts” services are running on both servers.

-I have granted Full Control to “HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib” for “Local Service”, “Performance Log Users”, and “Performance Monitor Users”.

-I have tested changing the “Performance Logs and Alerts” service to run under a different service account, but this doesn’t work.  I have seen perfmon working in other environments, w/o having to make this change.

-Tested connecting w/ “\\” in front of the name, FQDN, and IP.  Tested connecting directly to the name, FQDN, and IP.  Tested connecting to C$, admin$, and a manually created share.

-Verified “Local Service” is set in “Log on as batch job” in local sec policy

-Through the course of making changes, I’ve restarted services and rebooted the machines numerous times.

 Every forum I’ve checked online seems to end w/ “has anyone found a solution to this issue?”.  There are no events that get written to event logs for this error.

Does anybody have any ideas on this one?

 Thanks!