Suprised there is not a ton of information on google when i search for this but there is not. Lot of people asking the question but i none of them have any good answers.
I have a remote computer running hyper-v (server) running a Windows 7 x64 guest (guest). Occasionally i won't be able to remote desktop to guest. I will then remote to server and see that the guest instance is constantly using about 25% of the cpu. WHen i try to connect directly from server i will get the login screen but as soon as i type the password in it will just stay at the windows 7 login screen but the account names will disappear and it will not log in. It responds to pings though. I don't know how else to diagnose other than trying to run perfmon remotely. It only happens like every 3 weeks and i run it 24/7.
So i'm trying to run remote desktop remotely. I tested this out on a local vm i have running under vmware. When i try to connect using perfmon to my local vm i get this error:
"when attempting to connect to the remote computer the4 following system error occurred: the network path was not found"
I found in another past to start the remote registry service and when i start the service i get this error:
"No such interface supported"
Anyways, how do i remotely connect to another machine with perfmon or if anyone has a better idea how i can diagnose the problem above then let me know.
Best Answer
I'm 99.99% sure that perfmon just uses RPC. From a port perspective, this needs access to port 135 on the target (RPC server), but then subsequent access to an ephemeral port. The Windows firewall deals with this quite nicely, as it can follow the conversation from the RCP endpoint mapper (TCP 135) to the subsequent communication port.
However, the issue you're describing above is nothing to do with connectivity. A Windows server that's still responding to PING, but can't be RDP'd to, and gets "the network path was not found" is almost certainly experiencing kernel resource starvation.
Quite often, these situations come and go, but it can be frustrating and challenging to diagnose.
I'd start with:
Good luck!