Page 1 of 1

client (windows) active push to the server - how to?

Posted: Wed Dec 10, 2014 1:02 pm
by lejeczek
a newbie here :) who wonders if it's possible to gather some info and then actively push it to the server?
alternatively, the only bit known to the server would be client's MAC address - it this helps/matters.
I understand plethora is possible with the means of scripting/coding but I wonder if any client by default offers a typical way achieving it.
many thanks.

Re: client (windows) active push to the server - how to?

Posted: Wed Dec 10, 2014 1:29 pm
by slansing
So, it sounds like you may be looking at passive checks, where a windows event is fired off to run a series of plugin checks, then that data is pushed to Nagios. Please correct me if this is not what you meant. If it is, you could use the NRDP portion of NCPA to do this, or a number of other tools/agents such as NSCA:

http://assets.nagios.com/downloads/ncpa ... ation.html

Re: client (windows) active push to the server - how to?

Posted: Thu Dec 11, 2014 3:29 am
by lejeczek
this is exactly what I'm after, thanks!
Would it be also possible to somehow validate / authenticate a client so the server would accept only certain clients but ignore the others?

Re: client (windows) active push to the server - how to?

Posted: Thu Dec 11, 2014 10:21 am
by tmcdonald
NRDP uses a token, and NSCA uses encryption, so either of those two agents could be used.

Re: client (windows) active push to the server - how to?

Posted: Fri Dec 12, 2014 6:31 am
by lejeczek
many thanks, last question - see Nagios uses IPs all over the place, my scenario does not know about clients/agents IPs (may include MACs) in this passive setup. I hope this not a problem?

Re: client (windows) active push to the server - how to?

Posted: Fri Dec 12, 2014 10:17 am
by tmcdonald
In a passive scenario, Nagios doesn't really need to know about the IP of the remote machine. What matters is the passive results that are sent back. The message will specify the host and service, so the IP is irrelevant. This is why passive checks work so well for DHCP clients.