not able to monitor windows 2008 server

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
jtintegration
Posts: 56
Joined: Tue Nov 19, 2013 5:01 pm

Re: not able to monitor windows 2008 server

Post by jtintegration »

Here is my complete nsclient config file and it still does not work:

# If you want to fill this file with all available options run the following command:
# nscp settings --generate --add-defaults --load-all
# If you want to activate a module and bring in all its options use:
# nscp settings --activate-module <MODULE NAME> --add-defaults
# For details run: nscp settings --help


; Section for NSClient (NSClientServer.dll) (check_nt) protocol options.
[/settings/NSClient/server]

; ENABLE SSL ENCRYPTION - This option controls if SSL should be enabled.
use ssl = 0

; PERFORMANCE DATA - Send performance data back to Nagios (set this to 0 to remove all performance data).
performance data = 1

; PORT NUMBER - Port to use for check_nt.
port = 12489
; TODO
[/settings/default]

; Undocumented key
password = FPRi5c9ZQmCCOZll

; Undocumented key
allowed hosts = 10.1.13.143


; TODO
[/settings/NRPE/server]
; PORT NUMBER - Port to use for check_nt.
port = 12489

; Undocumented key
ssl options = no-sslv2,no-sslv3

; Undocumented key
verify mode = peer-cert

; Undocumented key
insecure = false


; TODO
[/modules]
NSClientServer = 1

; Undocumented key
CheckExternalScripts = 1

; Undocumented key
CheckHelpers = 1

; Undocumented key
CheckEventLog = 1

; Undocumented key
CheckNSCP = 1

; Undocumented key
CheckDisk = 1

; Undocumented key
CheckSystem = 1

; Undocumented key
NRPEServer = 1


And scrrenshoot of Nagios is included
You do not have the required permissions to view the files attached to this post.
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: not able to monitor windows 2008 server

Post by rkennedy »

I'm not sure why your NRPE is running on port 12489. Change this to 5666. Then restart the service, they're probably fighting for who gets to listen.

Code: Select all

; TODO
[/settings/NRPE/server]
; PORT NUMBER - Port to use for check_nt.
port = 12489
After doing so, try again. If that doesn't work, post your config + the nsclient log file once again.
Former Nagios Employee
jtintegration
Posts: 56
Joined: Tue Nov 19, 2013 5:01 pm

Re: not able to monitor windows 2008 server

Post by jtintegration »

It still does not work when I changed the port to 5666. Please take a look at the screenshot of nsclient.ini and screenshoot of nagios ofr those windows services.

# If you want to fill this file with all available options run the following command:
# nscp settings --generate --add-defaults --load-all
# If you want to activate a module and bring in all its options use:
# nscp settings --activate-module <MODULE NAME> --add-defaults
# For details run: nscp settings --help


; Section for NSClient (NSClientServer.dll) (check_nt) protocol options.
[/settings/NSClient/server]

; ENABLE SSL ENCRYPTION - This option controls if SSL should be enabled.
use ssl = 0

; PERFORMANCE DATA - Send performance data back to Nagios (set this to 0 to remove all performance data).
performance data = 1

; PORT NUMBER - Port to use for check_nt.
port = 5666
; TODO
[/settings/default]

; Undocumented key
password = FPRi5c9ZQmCCOZll

; Undocumented key
allowed hosts = 10.1.13.143


; TODO
[/settings/NRPE/server]
; PORT NUMBER - Port to use for check_nt.
port = 12489

; Undocumented key
ssl options = no-sslv2,no-sslv3

; Undocumented key
verify mode = peer-cert

; Undocumented key
insecure = false


; TODO
[/modules]
NSClientServer = 1

; Undocumented key
CheckExternalScripts = 1

; Undocumented key
CheckHelpers = 1

; Undocumented key
CheckEventLog = 1

; Undocumented key
CheckNSCP = 1

; Undocumented key
CheckDisk = 1

; Undocumented key
CheckSystem = 1

; Undocumented key
NRPEServer = 1
You do not have the required permissions to view the files attached to this post.
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: not able to monitor windows 2008 server

Post by rkennedy »

rkennedy wrote:I'm not sure why your NRPE is running on port 12489. Change this to 5666. Then restart the service, they're probably fighting for who gets to listen.

Code: Select all

; TODO
[/settings/NRPE/server]
; PORT NUMBER - Port to use for check_nt.
port = 12489
After doing so, try again. If that doesn't work, post your config + the nsclient log file once again.
You changed the wrong part. NSClient runs on 12489, and NRPE on 5666. See above.
Former Nagios Employee
jtintegration
Posts: 56
Joined: Tue Nov 19, 2013 5:01 pm

Re: not able to monitor windows 2008 server

Post by jtintegration »

I am still having problem with monitoring my Windows 2008 with NSClient. Can someone help? thanks
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: not able to monitor windows 2008 server

Post by rkennedy »

jtintegration wrote:I am still having problem with monitoring my Windows 2008 with NSClient. Can someone help? thanks
rkennedy wrote:
rkennedy wrote:I'm not sure why your NRPE is running on port 12489. Change this to 5666. Then restart the service, they're probably fighting for who gets to listen.

Code: Select all

; TODO
[/settings/NRPE/server]
; PORT NUMBER - Port to use for check_nt.
port = 12489
After doing so, try again. If that doesn't work, post your config + the nsclient log file once again.
You changed the wrong part. NSClient runs on 12489, and NRPE on 5666. See above.
You are not following directions on what should be changed, so it's hard to say what the problem is at this point. I would review the following documents as they btoh contain quite a bit of good information for teaching you about how to configure NSClient++ with NRPE -
https://assets.nagios.com/downloads/nag ... ios-XI.pdf
https://assets.nagios.com/downloads/nag ... ios-XI.pdf
Former Nagios Employee
tmcdonald
Posts: 9117
Joined: Mon Sep 23, 2013 8:40 am

Re: not able to monitor windows 2008 server

Post by tmcdonald »

Just checking in since we have not heard from you in a while. Did @rkennedy's post clear things up or has the issue otherwise been resolved?
Former Nagios employee
Locked