When I use performance counter test, if the target is local machine(Hostmonitor server itself), then it can get all counters.
If the target is a remote server, then it can't be connected and get counters.
I have test with windows support tool (extensible counter list), it's the same.
PS : Hostmonitor server is login with domain administrator.
However, when I test windows support tool (extensible counter list) on domain controller server, then it can connect to the remote server and get all counters.
What's the problem?
Do I need to add/change some authorization setting?
Best Regards,
Frank
Problem of performance counter test
-
- Posts: 7
- Joined: Mon Jan 05, 2009 4:00 am
- Location: TAIWAN
-
- Posts: 7
- Joined: Mon Jan 05, 2009 4:00 am
- Location: TAIWAN
Hi, Alex,
Thanks to your reply.
My problem as below:
HostMonitor server and remote server are all windows 2003 server.
Performance counter test
1.test on local server(Hostmonitor server itself), it's ok, it can get all counters.
2.test to a remote server, it can't connect to that remote server. (use domain administrator account, and remote registry service on the remote server is started)
Test with windows support tool (extensible counter list), the result is same as above.
So, I install RMA agent on remote server now, and use it to get performance counter.
But I hope that I can use performance counter test directly, not by RMA Agent.
Do I miss some setting? or need to add/change some authorization setting?
Thanks to your reply.
My problem as below:
HostMonitor server and remote server are all windows 2003 server.
Performance counter test
1.test on local server(Hostmonitor server itself), it's ok, it can get all counters.
2.test to a remote server, it can't connect to that remote server. (use domain administrator account, and remote registry service on the remote server is started)
Test with windows support tool (extensible counter list), the result is same as above.
So, I install RMA agent on remote server now, and use it to get performance counter.
But I hope that I can use performance counter test directly, not by RMA Agent.
Do I miss some setting? or need to add/change some authorization setting?
-
- Posts: 7
- Joined: Mon Jan 05, 2009 4:00 am
- Location: TAIWAN
Basically for Performance Counter related problem you should check the following items:
1) you are using account with admin rights for this test
2) RPC service is started on both systems (system where RMA is running and target host)
3) Remote Registry service should be started on target system as well
4) Check if account that you are using for the test has KEY_READ access to the following registry key on target system: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows_NT\CurrentVersion\Perflib.
To view/change permissions to the registry key you can use the registry editor utility (Regedt32.exe).
5) no firewall between 2 system blocks TCP ports above 1024
6) appropriate performance DLL should be enabled on target system
If HostMonitor shows "Cannot connect" error while you can connect from domain controller to target system then you can skip some steps.
Could you check is there firewall between HostMonitor and target system?
Probably both systems (HostMonitor and target system) located in the same network, so no firewall between them? The same domain?
Is RPC service started on system where HostMonitor is running?
Have you specified admin account for the test itself using "Connect as" test property or Connection Manager?
Usually we recommend using Connection Manager:
http://www.ks-soft.net/hostmon.eng/mfra ... htm#conmgr
Regards
Alex
1) you are using account with admin rights for this test
2) RPC service is started on both systems (system where RMA is running and target host)
3) Remote Registry service should be started on target system as well
4) Check if account that you are using for the test has KEY_READ access to the following registry key on target system: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows_NT\CurrentVersion\Perflib.
To view/change permissions to the registry key you can use the registry editor utility (Regedt32.exe).
5) no firewall between 2 system blocks TCP ports above 1024
6) appropriate performance DLL should be enabled on target system
If HostMonitor shows "Cannot connect" error while you can connect from domain controller to target system then you can skip some steps.
Could you check is there firewall between HostMonitor and target system?
Probably both systems (HostMonitor and target system) located in the same network, so no firewall between them? The same domain?
Is RPC service started on system where HostMonitor is running?
Have you specified admin account for the test itself using "Connect as" test property or Connection Manager?
Usually we recommend using Connection Manager:
http://www.ks-soft.net/hostmon.eng/mfra ... htm#conmgr
Regards
Alex