Home » CodeProject » Connect PerfMon to a Remote Server

Connect PerfMon to a Remote Server

It seems to be a simple & easy thing to connect Perfmon to a remote server.

GO TO RUN > Perfmon > Right Click “Connect to Another Computer” > Enter server name & you are done

But I face several connectivity issue during connecting Perfmon from remote server.

ISSUE 1: DNS not able to resolve the server name

RESOLUTION : I have fixed the issue by adding an entry in the hosts file (C:\Windows\System32\drivers\etc).

ISSUE 2 : Unable to connect the server

RESOLUTION: I have checked & found that Perfmon is trying to use Port 445 for connectivity. Telnet showed that port number 445 is blocked. I have asked added port into firewall exception & it works.

ISSUE 3 : Server Access denied

RESOLUTION: PerfMon is trying to the connect the remote server using the logged in user account which will not work by default as my user is not having access on remote server. Now, I need to run perfmon using a different user account which has access to the remote server.

runas /netonly /user:TestDomain\UserName “perfmon”
On running this command, it will ask for the password. It will open the PerfMon and you are ready to go.


If you liked this post, do like on Facebook at http://www.facebook.com/mssqlfun

Reference : Rohit Garg (http://mssqlfun.com/)

1 Comment

  1. Something here is very strange.

    First, your inability to resolve the DNS name. Understandable if you are not in a domain, but very odd considering you are. While manually putting an entry into the HOSTS file will solve the symptom, it’s actually hiding a larger problem.

    While using RUNAS /NETONLY will get you access to the server under a different user name; why doesn’t your account have access to the target server?

    I’m guessing that your user account isn’t a member of the “Performance Log Users” or “Administrators” group on the target machine. (membership in the “Performance Log Users” group is the minimum required security rights… don’t start adding members to the “Administrators” group.

    I’d look into why your DNS name resolution isn’t working.

Leave a Reply

Join us on Facebook

%d bloggers like this: