<div>Thanks Andreas, Good Description of the differences,</div>
<div> </div>
<div>However, you forgot to mension NC_Net also supports NSCA for Passive checks.</div>
<div> </div>
<div>So in my eyes, each flavor of the current Windows Plugins offers a different set of enhancements, </div>
<div> </div>
<div>NSCLIENT++ has NRPE and some other enhancements</div>
<div>NC_NET has NSCA, event logs, RunScripts,WMI,... (And supports Whitespace in Service names)</div>
<div>OpMon - may be introducing NRPE soon? and hopefully other enhancements </div>
<div> </div>
<div>All three are compatible to the Check_NT from the official Plugins and should return similar results.</div>
<div> </div>
<div>Tony (Author of NC_Net)<br><br></div>
<div class="gmail_quote">On Nov 9, 2007 5:35 AM, Andreas Ericsson <<a href="mailto:ae@op5.se">ae@op5.se</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div class="Wj3C7c">Giles Coochey wrote:<br>>> Steve Ensley wrote:<br>>>> I'm upgrading another departments Nagios 1.3 instance to Nagios 2.9.<br>>> they<br>>>> are using nsclient to get some info from some nt servers. Most of
<br>> my<br>>> Nagios<br>>>> experience has been monitoring Unix servers.<br>>>><br>>>> The website at <a href="http://nsclient.ready2run.nl/" target="_blank">http://nsclient.ready2run.nl/
</a> for nsclient doesnt<br>> seem to<br>>>> have been touched since 2004. Is it still a viable method to<br>> monitor nt<br>>>> servers or is there somthing else I should be looking into to<br>> replace
<br>>> it.<br>>> Try NSClient++ instead. It's at sourceforge somewhere, and is quite a<br>> lot<br>>> fresher. NSClient might work, but it's getting rather ancient.<br>>><br>><br>> I had this same quandary sometime back.
<br>><br>> Options were<br>><br>> NSClient (seems too old, not being developed)<br>> NSClient++ (presumably enhanced in some way)<br>> OpServices version of NSClient (still being developed)<br>> NC_Net (still being developed)
<br>><br>> In the end I simply went with NC_Net and it appears to work for us just<br>> fine, and I often see the author on this list, which tells me that he's<br>> still involved with Nagios in some way.<br>
><br>> It would be nice if all the different people who independently developed<br>> all the different versions 'unforked' their efforts though :-), it would<br>> make the decision on which one to use much easier, by having a lack of
<br>> choice!!<br><br></div></div>They aren't really forks. OpServices have simply taken over maintainership<br>of NSClient (more or less, as the original author seems to have vanished).<br>NSClient++ is a re-implementation in C++, with support for NRPE style script
<br>based checks as well. NC_Net does things through dot net stuff and some m$<br>voodoo, but incorporates the NSClient mode of address since that's what the<br>official plugins support.<br><br>So it's really three different agents.
<br>
<div class="Ih2E3d"><br>--<br>Andreas Ericsson <a href="mailto:andreas.ericsson@op5.se">andreas.ericsson@op5.se</a><br>OP5 AB <a href="http://www.op5.se/" target="_blank">www.op5.se
</a><br>Tel: +46 8-230225 Fax: +46 8-230231<br><br>-------------------------------------------------------------------------<br></div>
<div>
<div></div>
<div class="Wj3C7c">This SF.net email is sponsored by: Splunk Inc.<br>Still grepping through log files to find problems? Stop.<br>Now Search log events and configuration files using AJAX and a browser.<br>Download your FREE copy of Splunk now >>
<a href="http://get.splunk.com/" target="_blank">http://get.splunk.com/</a><br>_______________________________________________<br>Nagios-users mailing list<br><a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net
</a><br><a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a><br>::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
<br>::: Messages without supporting info will risk being sent to /dev/null<br></div></div></blockquote></div><br>