Passive service checks on windows via NAT

[Jan Scholten]

  > My problem is as follows. Most of our clients are behind firewalls
> which are providing NAT to the outside world. I can therefore setup
> nrpe_nt to check one remote server (creating a rule on the remote
> firewall so that incoming port 5666 gets forwarded to the nt server to
> be checked). However, this obviously won't work if the client site has
> two or more windows servers. VPN is out of the question, as well as
> setting up a remote nagios box at the client site.
You can: use nrpe_nt on different ports and forward maybe port 10000 to 
Server1 10001 to server 2 100003 to server 3 .. should work.


> My impression is that the checks will need to be run passively from
> the windows boxes themselves using nsca. So my question is:

It's probably the better solution.

> Can i get the checks/functionality of nrpe_nt passively ?. That is,
> can the nrpe_nt service be told to send data back to the nagios server
> without first receiving an active trigger from nagios ?. If this isn't
> possible, does anybody know of any way to do passive checks from
> windows boxes ?.
I believe (have not tried yet, but will!)
Use WinCron (to execute a script/programnm every some minutes)
let the script execute the checks, wrap the output and send it with 
send_nsca back to the nagios server.


> Any help would be greatly appreciated, as i'm now having recurring
> dreams about passive/active, and nrpe, and nsca ! :-)

I knwo what you mean..
Jan


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
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