Accessing windows core OS Perfmon from windows 11

P Mowleeswaran 20 Reputation points
2024-08-21T06:26:21.5233333+00:00

Hi Team,

I'm using windows 2022 core server as my domain controller and windows 11 as client machine, I don't have GUI to set performance collector in windows 2022 core machine. so i need to set Data collector set and manage the windows 2022 core servers system performance data as user defined or system defined from windows 11 by using connect to another computer.

i have allowed port 135,445 through firewall and remote registry, remote procedure call (RPC) services are running in the windows 2022 core server, but still getting "The RPC Server is unavailable" error, can you help me to fix this issue.

Regards,

Mowlee

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,943 questions
Windows 11
Windows 11
A Microsoft operating system designed for productivity, creativity, and ease of use.
9,464 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Yanhong Liu 8,060 Reputation points Microsoft Vendor
    2024-08-22T08:07:54.1966667+00:00

    Hi,

    Thanks for posting in the Q&A forum.

    The RPC service is using port 135. Maybe it doesn't work after you enable it through the firewall and registry

    You can try to test port 135 with telnet ip 135 command.

    Or filter port 135 with network monitor and see if it has network traffic coming back from both your machines.

    Best regards

    Yanhong

    =========================================

    If the answer is helpful, please click "Accept answer" and upvote it.


  2. P Mowleeswaran 20 Reputation points
    2024-08-22T08:20:16.17+00:00

    Hello,

    Thank you for your response. I have fixed this issue myself. I found that the Microsoft Event Viewer displays the following message from the windows 11:

    "DCOM got error '2147944122' from the computer xxx.xxxxx.org when attempting to activate the server."

    I applied the default firewall rule, COM+ Network Access (DCOM In), to permit DCOM connections on TCP port 135 instead of using a custom rule, and it is now working.

    Regards,

    Mowlee

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.