Unable to add AWS Windows Server for monitoring

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
priyadhole
Posts: 2
Joined: Wed Feb 23, 2022 3:03 am

Unable to add AWS Windows Server for monitoring

Post by priyadhole »

Hello Team,

Unable to add windows server into nagios XI.
giving me "CRITICAL - Socket timeout" error for services.

Both Nagios server and windows machine both are in same vpc and having same subnet.

tried to add windows server with NSclient++,NCPA

Thanks in adv.
gormank
Posts: 1114
Joined: Tue Dec 02, 2014 12:00 pm

Re: Unable to add AWS Windows Server for monitoring

Post by gormank »

Try running nmap -Pn from nagios to the windows host and post the nsclient/ncpa config from the windows host. Is the service running?
priyadhole
Posts: 2
Joined: Wed Feb 23, 2022 3:03 am

Re: Unable to add AWS Windows Server for monitoring

Post by priyadhole »

Please find the output from nagios server to windows in attached SS.

installed NClient++ is installed by using below link :
https://assets.nagios.com/downloads/nag ... ios-XI.pdf

the output of nsclient/nspa config
C:\Program Files\NSClient++>nsclient config
'nsclient' is not recognized as an internal or external command,
operable program or batch file.

Code: Select all

C:\Program Files\NSClient++>ncpa config
'ncpa' is not recognized as an internal or external command,
operable program or batch file.
kindly guide me. Thanks in adv.
Attachments
Linux to Windows.PNG
gormank
Posts: 1114
Joined: Tue Dec 02, 2014 12:00 pm

Re: Unable to add AWS Windows Server for monitoring

Post by gormank »

Have a look at you nsclient.ini, see what the port it will listen on and check allowed hosts. That should list you nagios server addresses or subnets.
Once you know the port and have set the allowed hosts look at windows services for nsclient and verify it's running.
From a windows cmd prompt try
netstat -an | find "port number from nsclient.ini"
Then from the shell on the nagios host
nmap -p<port number from nsclient.ini> <windows host IP>
If the windows host is listening on the port, and nagios doesn't see it as open, you may have a firewall between nagios and the windows host.
Maybe try
systemctl stop firewalld
on the nagios host and try again.
Locked