check_nt services not responding

[Joel Roberts]

I've installed Nagios on a Debian Etch server and it seems to be working
well, just a couple of things. Monitoring a Windows box, I've installed
the NSClient++, for some reason there's no icon in the SysTray, but the
service is up and running. Most of the Services respond, except the
following:

 

Drive space, CPU Load, Explorer and W3SVC

 

I've verified the configuration file, but the Status Info in Nagios
returns the following:

 

Usage:check_nt -H host -v variable [-p port] [-w warning] [-c
critical][-l params] [-d SHOWALL] [-t timeout] 

 

Here are the entries in the windows.cfg file, Memory Usage works, Drive
Space does not:

 

define service{

        use                     generic-service

        host_name               lwsyslog1

        service_description     Memory Usage

        check_command           check_nt!MEMUSE!-w 80 -c 90

        }

define service{

        use                     generic-service

        host_name               lwsyslog1

        service_description     C:\ Drive Space

        check_command           check_nt!USEDDISKSPACE!-1 c -w 80 -c 90

        }

 

Thanks in advance,

 

Joel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20071004/45eef7ab/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at 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