Page 1 of 1

check_nt problem

Posted: Tue Dec 09, 2014 10:01 pm
by deepshikha20
Hi,

I have added remote windows hosts and facing the below error

]:/usr/local/nagios >/usr/local/nagios/libexec/check_nt -H 10.25.0.0 -p 12489 -v MEMUSE
NSClient - ERROR: Invalid password.
[]:/usr/local/nagios >/usr/local/nagios/libexec/check_nt -H 10.25.0.0 -p 12489
check_nt: Could not parse arguments
Usage:
check_nt -H host -v variable [-p port] [-w warning] [-c critical]
[-l params] [-d SHOWALL] [-u] [-t timeout]
[]:/usr/local/nagios >
]:/usr/local/nagios >


My check_nt command
define command{
command_name check_nt
command_line $USER1$/check_nt -H $HOSTADDRESS$ -p 12489 -s password -v $ARG1$ $ARG2$
}

Please help !

thanks

Re: check_nt problem

Posted: Wed Dec 10, 2014 3:36 am
by Box293
It looks like you have a password on the remote host.

Passwords need to be provided with the -s argument.

Code: Select all

/usr/local/nagios/libexec/check_nt -H 10.25.0.0 -p 12489 -s password -v MEMUSE
Please post your nsclient.ini or nsc.ini file here.

Re: check_nt problem

Posted: Thu Dec 11, 2014 3:11 am
by deepshikha20
Please find the attached log.

Sometimes it works and sometimes it won't work and throw an error invalid password.

And one more query , I have added a new host but it is not visible on the web interface and sometimes it's visible .

I have attached the screenshot for your reference.

Please check.

Thanks.

Deepshikha

Re: check_nt problem

Posted: Thu Dec 11, 2014 10:47 am
by slansing
You will need to ask that second question in a new thread so we stay on topic. As for check_nt, are you sure that it is erroring out and telling you invalid password some of the time? That sounds like something that would either work, or be invalid until changed. Nobody is modifying the nsc.ini file on the windows system? And is any other application/service hopping listening or sending on port 12489? From the log, looks like its really always showing you invalid password, not just some of the time. You will need to define the correct password in the nsc.ini file for check_nt, then restart the nsclient service. You also need to verify that ALL of your service checks against this host in Core, that use check_nt, have that password defined.