My only guess, then, is that you have different encryption/encoding
settings between the two. Strange that this would only affect the CPU
check, though. Since I've never encountered any problems with nsclient
I've never needed to look into debugging...
My only remeaining suggestion is to try installing nsclient++ or nc_net
and see if they work, or if it still fails then the problem lies with
your check_nt call. Double check that you are really passing meaningful
parameters to check_nt.
Steve
--
Steve Shipway
ITSS, University of Auckland
(09) 3737 599 x 86487
[EMAIL PROTECTED]
I did not modified the password.
I am checking correctly (on the same host) memory and disk
spaces.
On other hosts I can check correctly also the CPULOAD.
Marco
________________________________
The client is sending None&2&5 which is correct for a 5-min CPU
average request with the default password.
If you have modified the password on the pnsclient agent then
this may be the cause (this is done in the registry). Alternatively
check your check_nt program as it may be more recent and not compatible?
We use nagios-plugins 1.4 and this works with pnsclient2.0.1 correctly.
Steve
I installed NsClient (2.0.1) on a Windows 2000 server.
It is working fine, but if I want to check CPULOAD I will read following
error message:
NSClient - ERROR:Malformed request or internal error.
Check EventLog:None&2&5
Nagios server is a 1.4 version
Have you got any idea?
Thanks !
Marco
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Nagios-users mailing list
Nagios-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
