[Nagios-users] Monitoring Wimdows machines

2009-12-22 Thread stan
We have a fair sized Nagios installation that currently only monitors UNIX
machines, and we want to add some Windows clients, primarily XP. We started
down the road using NSClient++ using the check_nt Nagios plugin, but
haven't been able to communicate with any XP boxes.  The NSClient++ web
page suggests using the NRPE method which has us wondering if the check_nt
method even works.  Has anyone had success with either of these methods and
if so which?  Perhaps there is another tool that someone can recommend.

Thanks in advance,
Stan Brown

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
___
Nagios-users mailing list
Nagios-users@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


Re: [Nagios-users] Monitoring Wimdows machines

2009-12-22 Thread Assaf Flatto
I've had success on both counts , and the check_nt works with no issues.

points to consider that might be causing the problem :
in the nsc.ini , did you allow the nagios server in the allowed hosts , 
did you specify the port that you initiate the checks on ?

if you did any modification to the nsc.ini , did you restart the 
nsclient++ service ?

have you disabled or allowed connection on the port on the internal 
windows firewall?

Assaf

stan wrote:
 We have a fair sized Nagios installation that currently only monitors UNIX
 machines, and we want to add some Windows clients, primarily XP. We started
 down the road using NSClient++ using the check_nt Nagios plugin, but
 haven't been able to communicate with any XP boxes.  The NSClient++ web
 page suggests using the NRPE method which has us wondering if the check_nt
 method even works.  Has anyone had success with either of these methods and
 if so which?  Perhaps there is another tool that someone can recommend.

 Thanks in advance,
 Stan Brown

   

--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
___
Nagios-users mailing list
Nagios-users@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


Re: [Nagios-users] Monitoring Wimdows machines

2009-12-22 Thread Natxo Asenjo
On Tue, Dec 22, 2009 at 4:08 PM, stan st...@panix.com wrote:
 We have a fair sized Nagios installation that currently only monitors UNIX
 machines, and we want to add some Windows clients, primarily XP. We started
 down the road using NSClient++ using the check_nt Nagios plugin, but
 haven't been able to communicate with any XP boxes.  The NSClient++ web
 page suggests using the NRPE method which has us wondering if the check_nt
 method even works.  Has anyone had success with either of these methods and
 if so which?  Perhaps there is another tool that someone can recommend.

nsclient++ works fine with xp. You need to check the ini file and
verifying you are using the correct ports on the xp machines and the
nagios server. Check the xp firewall as well, standard since sp 2 the
xp machines are firewalled (unless you have already disabled that).

-- 
natxo

--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
___
Nagios-users mailing list
Nagios-users@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


Re: [Nagios-users] Monitoring Wimdows machines

2009-12-22 Thread stan
On Tue, Dec 22, 2009 at 04:22:17PM +, Assaf Flatto wrote:
 I've had success on both counts , and the check_nt works with no issues.
 
 points to consider that might be causing the problem :
 in the nsc.ini , did you allow the nagios server in the allowed hosts , 
 did you specify the port that you initiate the checks on ?
 
 if you did any modification to the nsc.ini , did you restart the 
 nsclient++ service ?
 
 have you disabled or allowed connection on the port on the internal 
 windows firewall?
 
 Assaf
 

Yes, we have done all of these. We do live in a world with way too many
firewalls. What ports should we check with nmap between the 

What else can you think of that we might need to check?

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
___
Nagios-users mailing list
Nagios-users@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


Re: [Nagios-users] Monitoring Wimdows machines

2009-12-22 Thread Michael Medin

Read the guide it should have the information you need to get it setup.

http://nsclient.org/nscp/wiki/doc/usage/nagios/nrpe

// Michael Medin

stan wrote:

On Tue, Dec 22, 2009 at 04:22:17PM +, Assaf Flatto wrote:
  

I've had success on both counts , and the check_nt works with no issues.

points to consider that might be causing the problem :
in the nsc.ini , did you allow the nagios server in the allowed hosts , 
did you specify the port that you initiate the checks on ?


if you did any modification to the nsc.ini , did you restart the 
nsclient++ service ?


have you disabled or allowed connection on the port on the internal 
windows firewall?


Assaf




Yes, we have done all of these. We do live in a world with way too many
firewalls. What ports should we check with nmap between the 


What else can you think of that we might need to check?

  


--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev ___
Nagios-users mailing list
Nagios-users@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

Re: [Nagios-users] Monitoring Wimdows machines

2009-12-22 Thread stan
On Tue, Dec 22, 2009 at 10:54:14PM +0530, Kumar, Ashish wrote:
  Yes, we have done all of these. We do live in a world with way too many
  firewalls. What ports should we check with nmap between the
 
  What else can you think of that we might need to check?
 
 
 Try this:
 
 edit nsc.ini, in the log section uncomment debug and file options, e.g.
 [log]
 debug=1
 file=NSC.log
 
 restart nsclient++.
 
 from nagios server run a command like
 $ check_nt -H $HOST -p $PORT -s $PASSWORD -v UPTIME
 
 post the output of check_nt command and output of NSC.log, if any.

To clse the thread. We had 2  problesm. We had odd networking, and the
nagios machine is dual hiomed. We had put the wrong IP in the config on the
Windows machine, but fixing that did not make it work. We had to tell the
windows client what IP to bind on (it's only interface BTW). It is a
virtualbox machine, with a bridged interface from the host, so mayvbe that
had something to do with it.

Thanks for the help!
-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev 
___
Nagios-users mailing list
Nagios-users@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