additional comonents for win services

[sharding]

using the nsclient for to monitor a windows box, standard I use the first two check boxesenable common plugins and the enable nsclient server (check_nt) box, if I want to monitor actual win services on these do I need any other options ?

If so which do I need and now some are already installed I assume it's easier to edit the nsclient.inf file so which sections.

as is when I try to monitor win services I get a cannot connect on a port mesage from nagiosxi (we have no firewalls internally)

[lmiltchev]

You can run the "Windows Server" monitoring wizard, and specify any services that should be monitored in Step 3 (under the "Services" section). Can you give us an example of a service that you are trying to monitor? Also, run the following commands and show us the output:

Code: Select all

nmap <client ip> -p 12489
/usr/local/nagios/libexec/check_nt -H <client ip> -s "<password>" -p 12489 -v CLIENTVERSION
/usr/local/nagios/libexec/check_nt -H <client ip> -s "<password>" -p 12489 -v SERVICESTATE -l "Spooler" -d SHOWALL

[jolson]

In addition to what lmiltchev has suggested,

Did you open the proper ports on your Windows Firewall? I believe the ports that need to be opened are 5666/nrpe and 12489/nsclient.

You shouldn't need any extra configuration in your nsclient.ini to monitor services - this type of check is typically handled by checkServiceState, which can monitor any service running on your Windows box.

If the above has been taken care of, check your nsclient.ini file to ensure that it includes:

Code: Select all

[/settings/default]
allowed hosts = NETADDR/NETMASK
password = nsclient

[/modules]
NSClientServer = 1
CheckSystem = 1
CheckDisk = 1
NRPEServer = 1

[/settings/NRPE/server]
use ssl = 1
payload length = 1024
allow nasty characters = false
allowed ciphers = ADH
ssl = 1
allow arguments = 1
insecure = 1

[sharding]

Original post did state NO FIREWALLS,

The suggested checks fail and checking ports in use using netstat shows a whole bunch as both servers are Antivirus servers which I know uses a huge range for management of enterprise and workstations so it's most likely I just can't do these checks on them, which is a massive shame as the AV services are exactly what I wanted to monitor.

[tmcdonald]

Changing the port should be no problem at all:

https://docs.nsclient.org/tutorial/core ... rpe-server

That section is for the NRPE listener within NSClient, but changing the port for NSClient proper is the same process.

What was the nmap output from lmiltchev's post?