> You could use NSCA. This is what I'm using to monitor Windows > servers that are behind other machines. > > The key requirement is that the Windows machines can make > outgoing connections. Your Nagios server will be passive, > only listening for the incoming connections. > > I've been using the NC_Net tool from http://www.shatterit.com/NC_Net/
Trouble is, the NC_Net requires us to install the whole .net framework and reboot the server - a major outage and the business wont allow it. They only just allow the pNSclient because it doesnt require a reboot and has such a tiny footprint. .net is a bit of a huge beast. We do use NSCA for some things -- eg, the windows eventlog agent, and some UNIX active checks. However, our entire setup is centrally confingured and managed, and so this sort of thing again breaks the standard pattern. I'm having a go at compiling the check_nt under windows, but it requires some major rewriting for winsock. Also, I'm trying to arrange some firewall changes (but thats even less likely to happen :) Thanks, Steve ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Nagios-users mailing list [email protected] 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
