Performance Counter problem

[Betelgeuse]

Hi

I'm curently running HostMonitor 6.10 on a Windows 2000, SP4 server.

I have been doing some test from our HostMonitor situated on our LAN to a server in our DMZ. They all worked fine until 2 days ago. The tests I'm performing are Performance Counter, File Size and CPU Usage.

The problem is that they now turns upp with Status 'Unknown', allways. The specific error message is 'Unable to connect to machine'

I have noticed something peculiar: when auditing the logons on the DMZ server, they shows that HostMonitor performs the logon to the DMZ server with the HostMonitor Service Account, and not the one I explicitly provided for each test (namely a local administrator account on the DMZ server). This of course fails..

I have tried to re-enter the logon credentiels, make new tests, reset both servers, use Hostname instead of IP-address, but nothing helps. Our WAN manager assures me that there is nothing on the firewall preventing my tests to perform, so I'm stuck.

I would appreciate if someone could come up with a solution to this problem.

Btw, ordinary Ping and SMTP tests perfoms just fine.

Regards
Betelgeuse

[KS-Soft Europe]

I have been doing some test from our HostMonitor situated on our LAN to a server in our DMZ. They all worked fine until 2 days ago.
The problem is that they now turns upp with Status 'Unknown', allways. The specific error message is 'Unable to connect to machine'

HostMonitor should be started under administrator's account in order to perform Performance Counter test.
Is Remote Registry service started on remote system?
Do you use RMA to perform tests or test is performed by HostMonitor itself?

Try to use Connection Manager:
http://www.ks-soft.net/hostmon.eng/mframe.htm#tests.htm

I have noticed something peculiar: when auditing the logons on the DMZ server, they shows that HostMonitor performs the logon to the DMZ server with the HostMonitor Service Account, and not the one I explicitly provided for each test (namely a local administrator account on the DMZ server). This of course fails..

I think, you should assign "Log on as Service" priviledge to the account, you have specified for each test. You may use gpedit.msc applet.

Regards,
Max

[Betelgeuse]

Thanks for a very quick response.

HostMonitor should be started under administrator's account in order to perform Performance Counter test.

HostMonitor is runned by an administrator account, has always been, and has not been changed.

Is Remote Registry service started on remote system?

It was disabled. I enabled it and started it, but still the same problem (Don't think it has been enabled before either, even when the tests were ok).

Do you use RMA to perform tests or test is performed by HostMonitor itself?

The test is performed by HostMonitor itself

I think, you should assign "Log on as Service" priviledge to the account, you have specified for each test. You may use gpedit.msc applet.

Done that too, but still not working..

I still don't understand why HostMonitor apparently tries to logon with the account running the HostMonitor Service, and not the account provided explicitly in the tests?

[KS-Soft Europe]

Is Remote Registry service started on remote system?

It was disabled. I enabled it and started it, but still the same problem (Don't think it has been enabled before either, even when the tests were ok).

Please make sure
1) RPC service is started on your systems
2) Remote Registry Service started on target system
3) PerfOS.DLL is enabled on target system
4) There are no firewalls between 2 systems

Microsoft provides "Extensible Counter List" utility: http://www.microsoft.com/downloads/deta ... laylang=en
This utility displays list of DLLs that are used to support Performance Counters, using the utility you may disable/enable specific DLLs.

Unfortunately Windows Performance Counters implementation is very unreliable. We spent a lot of time triyng to find some workaround and often this "workaround" works. As you see HostMonitor offers 4 options for Performance Counter test:
- MultiThread mode;
- OneByOne mode;
- Smart mode;
- External mode
(see Misc page in the Options dialog).
But some systems just don't work regardless of anything. We can redisign HostMonitor but we cannot fix Windows.

So, we would suggets you try WMI test method:
http://www.ks-soft.net/hostmon.eng/mfra ... ts.htm#wmi

I think, you should assign "Log on as Service" priviledge to the account, you have specified for each test. You may use gpedit.msc applet.

Done that too, but still not working..

You need to restart HostMonitor service.

Regards,
Max

[KS-Soft]

I still don't understand why HostMonitor apparently tries to logon with the account running the HostMonitor Service, and not the account provided explicitly in the tests?

Not HostMonitor but Windows. Some time ago we spent a lot of time investigating this problem. HostMonitor sends correct account information to Windows API but Windows may use current user acccount information instead (account that was used to start service). We did not find solution for this problem Just workaround: you may create the same account on remote system using the same username and password (if all systems in the same domain, its not a problem).

And Max is right - Windows Performance Counters is not reliable technology. That's why we have implemented WMI test method, it uses different technology and work much better

Regards
Alex

[KS-Soft]

It was disabled. I enabled it and started it, but still the same problem (Don't think it has been enabled before either, even when the tests were ok).

No way. If Remote Registry Service is stopped, another system cannot retrieve Performance Counters

Regards
Alex