To monitor memory usage by any process in windows host.

[bwallace]

"connection refused by host is usually a result of:
- Nothing is listening on the IP:Port you are trying to connect to.
- The port is blocked by a firewall.

What does netstat -an on the client machine reveal? Is port 5666 listening?
If it is listening, I'd suspect a firewall is to blame, you may need to open :5666 on it.

Let us know if this helps, thanks.

[RIDS_I2MP]

Hi Team,

I guess the earlier message arised because I have not enabled NRPE in NSclient++, now I have enabled nrpe by editing the NSC.ini file by uncommenting "NRPEListener.dll" and "CheckExternalScripts.dll".

Now I am receiving the attached message.

Please find the attached snapshot for output of netstat -an command.

kindly suggest.

[WillemDH]

nsc.ini?? What version of NSClient are you using? I would recommend using 0.4.1.105 or 0.5.0.46. The NSClient config file is called nsclient.ini there.

[rkennedy]

Updating might help as Willem mentioned, if it'll work on W2K3.

After doing so, or if it does not work, please post your nsclient configuration file for us to look at.

[tgriep]

You may also need to enable arguments for NSClient.
In the ini file on your windows system, make sure you have the following in the [NRPE] section.

Code: Select all

allow_arguments=1

[RIDS_I2MP]

Hi Team,

We are using below licence and version NSClient++
"GNU GENERAL PUBLIC LICENSE
Version 2, June 1991"

This monitoring will not work on this verion of NSClient++?

[tgriep]

That version number doesn't look right. It should be like 0.3.9.x or 0.4.x.x.
If you go to this folder on your windows server and right click the executable, you should get the version number.

Code: Select all

C:\Program Files\NSClient++

In that folder, there should be a nsc.ini or a nsclient.ini file. Can you post those and a nsclient.log file so we can review them?

Can you login to the XI server, run the following command and post the output?

Code: Select all

/usr/local/nagios/libexec/check_nrpe -H 10.147.108.140

This will tell us the version of the client and test basic connectivity.

[lmiltchev]

Version 2

Do you mean ver. 0.2?
I can see the following versions on the NSClient++ website - 0.3.x, 0.4.1, 0.4.2 (legacy), 0.4.3, 0.4.4, and 0.5.0...

[RIDS_I2MP]

Hi Team,

I am not able to find the Nsclient++ version by right clicking on the executable file at "C:/program files/nsclient++" folder.

I have executed the attached command and found the provided output, refer the attached snapshot.

I am also attaching the NSC.ini file and nsclient.log file.

Kindly suggest.

[tgriep]

There are some settings in the nsc.ini that need to be updated

Under the [modules] section
Change this from

Code: Select all

;NRPEListener.dll
;CheckExternalScripts.dll

to

Code: Select all

NRPEListener.dll
CheckExternalScripts.dll

Under the [Settings] section
Change this from

Code: Select all

allowed_hosts=10.147.108.46

to

Code: Select all

allowed_hosts=10.147.108.46, 10.148.160.4

Under the [NRPE] section
change this from

Code: Select all

;allow_arguments=0
;allow_nasty_meta_chars=0

to

Code: Select all

allow_arguments=1
allow_nasty_meta_chars=1

Save the file and restart the NSClient on the windows server.
Try your check again and see if it works now.