Forum Discussion
Get-Counter: Could not find any performance counter sets on the 192.168.50.101 computer: error 80000
Your ping test doesn't prove you have connectivity since Get-Counter does not use ICMP.
Get-Counter leverages SMB, which operates over TCP 445.
You've only provided the first part of the error code, but my guess is the full error code is 800007d0. If this is the case, then you have something blocking your ability to reach TCP 445. That could be a firewall on your client, a firewall on the target host, or even a firewall appliance somewhere between the two.
This is a Wireshark trace showing the repeated attempts to connect to TCP 445 during the connection attempt that ultimately fails with error 800007d0.
Once you get past the firewall issue, you still need to have sufficient rights on the target host. If you do not, you will fail with error c0000bdb, for which I've included the Wireshark trace showing the "access denied" error sent from the target host back to the client.
Cheers,
Lain
Your ping test doesn't prove you have connectivity since Get-Counter does not use ICMP.
Get-Counter leverages SMB, which operates over TCP 445.
You've only provided the first part of the error code, but my guess is the full error code is 800007d0. If this is the case, then you have something blocking your ability to reach TCP 445. That could be a firewall on your client, a firewall on the target host, or even a firewall appliance somewhere between the two.
This is a Wireshark trace showing the repeated attempts to connect to TCP 445 during the connection attempt that ultimately fails with error 800007d0.
Once you get past the firewall issue, you still need to have sufficient rights on the target host. If you do not, you will fail with error c0000bdb, for which I've included the Wireshark trace showing the "access denied" error sent from the target host back to the client.
Cheers,
Lain
I was confused at first because the get-counter command doesn't have parameters to pass username and password. Finally, I suddenly realized that I opened Windows Explorer, entered "\\virtual machine IP address" in the address bar, then entered the corresponding account password, and selected "Save Credentials", and then I ran the command again, this time it was successful!
Finally, you are so awesome, very professional and enthusiastic, thank you very much, I wish you all the best in your work and life.