NSClient on W2K

[Jeyri bautista]

Hi,

I configured nsclient on W2K, only I unzip the nsclient ic c:\nsclient  and
later I from command line in c:\nsclient\pnsclient\ I execute install

This show you a message satisfactory.

In the nagios you should configure the services witch the check_command
check_nt, and the parameters necesary for check cpu, mem or other value.

Jeyri

----- Original Message ----- 
From: "Marco Borsani" <m.borsani at it.net>
To: <nagios-users at lists.sourceforge.net>
Sent: Thursday, January 22, 2004 11:39 AM
Subject: [Nagios-users] NSClient on W2K


> Hi everybody.
>
> I need to configure NSClient on Windows 2000 systems.
> I installed the client but I have some problems to configure services
checks
> on my Unix server.
> Have you got any installation like my one in order to suggest me
something?
>
> Thanks a lot.
>
> Marco
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> 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



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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