Monitoring Wimdows machines

[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 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