Nagios Support Forum

Now that you are in the directory, and verified the plugins are there you should be able to run the commands:
-Should return something along the lines of "I (NSclient version and date) seem to be doing fine..."

And you should be able to run the actual check_nt check:
Once again.. return what the console outputs we need to see the exact output.

I tried what you suggested and still returned the No such file or directory. I noticed the ./ from the second command you mentioned and was able to get it to work with that preceding..

[root@localhost libexec]# /check_nrpe -H IPADDR
-bash: /check_nrpe: No such file or directory
[root@localhost libexec]# ./check_nrpe -H IPADDR
CHECK_NRPE: Socket timeout after 10 seconds.
[root@localhost libexec]# ./check_nt -H IPADDR -p 12489 -v UPTIME
CRITICAL - Socket timeout after 10 seconds

If I try the commands for an address that I am monitoring successfully I get the following:

[root@localhost libexec]# ./check_nt -H IPADDR -p 12489 -v UPTIME
NSClient - ERROR: Invalid password.
[root@localhost libexec]# ./check_nrpe -H IPADDR
I (0.3.9.328 2011-08-16) seem to be doing fine...

Apologies I forgot an execute append on the first command, now, you should be able to add your password into the uptime check, the password was set during the Agent installation, and can also be found in the NSC/NSclient.ini file in the agent's directory on the windows server.

To add a password to that command simply add the password flag "-s" followed by the password:

Here is the output:
./check_nt -H IPADDR -s password -p 12489 -v UPTIME
CRITICAL - Socket timeout after 10 seconds

And the output I get from an address I am monitoring successfully:
[root@localhost libexec]# ./check_nt -H IPADDR -s password -p 12489 -v UPTIME
System Uptime - 14 day(s) 10 hour(s) 10 minute(s)

Well, it appears that your plugins are just fine. Try: Do not try to run anything with the "xi_" prefix from the command line as they are mostly wrappers for XI of the actual plugins.

Isn't that what I just did..?

mobiledataforce wrote:Here is the output:
./check_nt -H IPADDR -s password -p 12489 -v UPTIME
CRITICAL - Socket timeout after 10 seconds

And the output I get from an address I am monitoring successfully:
[root@localhost libexec]# ./check_nt -H IPADDR -s password -p 12489 -v UPTIME
System Uptime - 14 day(s) 10 hour(s) 10 minute(s)

mobiledataforce wrote:Isn't that what I just did..?

Yeah, sorry about that. I had the thread open for a while in a tab and didn't refresh it

Lets check to see if the port is open:

On the XI system: This is most likely a client-side firewall/nsclient configuration issue.

[root@localhost ~]# nmap IPADDR -p 12489

Starting Nmap 5.51 ( http://nmap.org ) at 2013-04-11 12:36 MDT
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 4.56 seconds

I agree it is a client-side firewall/nsclient issue, or something like it. From what I can tell, it is configured properly; just as I have all the others which are monitoring without issue. There is no AV or firewall running locally, and I am certain ports 5666, 5667, 12489, echo, echo-reply are open/enabled on the outside firewall.

Hmm... odd, if you nmap that IP without the port and it goes through it has to be a port related issue at that point, I would try it without the port and see.

Here is the output, I had to append the -Pn to get it to go through, same was true for hosts I am monitoring successfully:

[root@localhost ~]# nmap IPADDR -Pn

Nmap scan report for IPADDR
Host is up.
All 1000 scanned ports on IPADDR are filtered

Nmap done: 1 IP address (1 host up) scanned in 203.16 seconds