<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7653.38"> <TITLE>RE: [Nagios-users] Nrpe and windows</TITLE> </HEAD> <BODY>  Brady, You can use NSclient++ also add a few more NSclient++ proxies. Write a wrapper script around check_nt to use multiple proxies instead of one. Regards, Naren -----Original Message----- From: Maxwell,Brady [<A HREF="mailto:maxwellb@oclc.org">mailto:maxwellb@oclc.org</A>] Sent: Wed 12/10/2008 2:05 AM To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] Nrpe and windows I have some questions for the group about nagios, nrpe, nrpe_nt.exe and windows. Some Background: We are currently using check_nrpe to send checks to an nrpe_nt.exe which then runs checks on about 350 windows servers and returns the output to nagios one service at a time, a total of about 1500 checks run this way. The servers are all one-offs and are not part of a ad auth domain. We have have issues like "[No output available from command...]: 128" on our "nrpe proxy". Rebooting the proxy server seems to fix this issue. According to what I have found via google there is some speculation that nrpe_nt.exe is not letting go of tcp ports it uses. I do not buy it. Since nrpe_nt.exe is not a current project anymore I was thinking maybe its time to find a new solution to check these servers. Is anyone using a similar configuration? Does anyone know of a more current project that can facilitate the same monitoring architecture? Thanks Brady </BODY> </HTML>