Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm currently running NSClient++ on Windows SBS 2003 and am having horrendous problems with time-outs from Nagios3 generating a load of warnings, etc.

I'm pretty sure that the errors are caused by load spikes on the SBS as, from time to time, we've had issues with Outlook connectivity as well.

Please bear in mind that reconfiguring / upgrading or generally doing anything drastic on the SBS is not an option as it's the core of the business and works, granted not very quickly but it works.

Are there alternatives to NSClient++ that work reliably and securely on Windows? Is SNMP an option? If there anything I should look at on the server side?


locked by HopelessN00b Dec 5 '14 at 12:36

This question exists because it has historical significance, but it is not considered a good, on-topic question for this site, so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. More info: help center.

up vote 0 down vote accepted

If you are having timeout issues due to load on the server, then I would submit that Nagios and the NSClient is working correctly. Other options will try to connect to the sever as well and have the same types of issues if it cannot respond due to load.

If you are getting an overload of notifications that you are positive will be going away, you may want to adjust the conditions that cause the warnings and the number of retries before the notifications are sent.

Similar to my original thoughts TBH. I'll take a look at the thresholds and see what I can do on the host to prevent the FP's from leaking through. – Rob Dudley May 29 '09 at 13:59

SNMP is a good option too. You need to add this using windows Add/Remove components, see here. Be aware that when you install this it will stop other services such as IIS, smtp, etc. so do this off hours or during a maintenance window.

Myself, I have found NSClient preferable because it is easy to access all the windows performance counters.

Thanks for the heads up regarding SNMP install (and associated Gotcha!) I assume that timeout will still be an issue even with SNMP but at least it's a pull solution and may prove more resilient than NSCLient - then again I do like the ease with which NSClient was setup – Rob Dudley May 29 '09 at 14:01

How are your timeouts configured?

You can set timeouts on the nrpe-command (check_nrpe -t ...). You can also configure timeouts in nsclient++ (socket_timeout=...).


Not the answer you're looking for? Browse other questions tagged or ask your own question.