Using check_nt with Windows 10

[satori7]

Has anyone else had issues monitoring Windows 10?

I installed NSClient++ and set it up the same way that I have on all my Windows Servers. I've shut down Windows Firewall and the network connection between my Nagios server and the Windows 10 box is fine. If I run check_nt from the command line I get this:

Code: Select all

[root@uranus plugins]# ./check_nt -H 172.17.2.22 -p 12489 -s ******** -v MEMUSE
could not fetch information from server

The same command returns just fine from all other NSClient++ boxes.

[hsmith]

Has anyone else had issues monitoring Windows 10?

I installed NSClient++ and set it up the same way that I have on all my Windows Servers. I've shut down Windows Firewall and the network connection between my Nagios server and the Windows 10 box is fine. If I run check_nt from the command line I get this:

Code: Select all

[root@uranus plugins]# ./check_nt -H 172.17.2.22 -p 12489 -s ******** -v MEMUSE
could not fetch information from server

The same command returns just fine from all other NSClient++ boxes.

What version of NSClient are you running?

Can you please post your nsclient.ini / nsc.ini, with important information obfuscated of course.

[satori7]

Well, I feel silly.

While I was copying the nsclient.ini to paste here, I noticed that I had fat fingered the IP. I could have sworn that I checked that.

Thanks anyway awesome Nagios community.

[hsmith]

Well, I feel silly.

While I was copying the nsclient.ini to paste here, I noticed that I had fat fingered the IP. I could have sworn that I checked that.

Thanks anyway awesome Nagios community.

Haha, it happens to the best of us! Thanks for letting us know!

and here I almost had my Windows 10 VM ready to test with....

[jdalrymple]

For the record books... no problem

Code: Select all

[jdalrymple@localhost ~]$ /usr/local/nagios/libexec/check_nt -H 192.168.5.233 -p 12489 -s nsclient -v CLIENTVERSION
NSClient++ 0.4.3.131 2015-02-15