NSClient++ and Connection refused error

[PhilG]

Hello:
I am using the latest NSClient++-0.3.9.328 (64 bit) and have installed it successfully on a couple of Windows servers that were on the same VLAN:
Windows Server 2008 Standard (64 bit)
Windows Server 2008 R2 Enterprise (64 bit)

and then setup monitoring in Nagios XI 2014R1.5 (won't update to R2.0 yet) using the Windows Server Wizard with no issues.

I then installed the client on about 4 different Windows servers, one in each different VLAN and with a different Windows OS version:
Windows Server 2012 Datacenter 64 bit
Windows 2008 R2 Enterprise SP1 64 bit

After the NSClient++ installs, I then setup monitoring for each of those servers using the Windows Server Wizard, but eventually the following errors appeared:
"connect to address <FQDN of my Windows server> and port 12489: Connection refused"

I found the following URL and read it, but it turned out that it was not the solution:
http://support.nagios.com/forum/viewtop ... 70&p=26733

I had my Network guy check the Firewall settings, and the monitoring server and all IPs in the different VLANs were allowed to communicate to each other with TCP and UDP port 12489.
I verified that regardless whether or not the local Windows firewall was on or off for the Domain, and that the exception for NSClient++ was allowed, that the problem was not a Windows firewall issue.

WHAT WAS THE COMMON ISSUE:
When I manually install the NSClient++ on a Windows server with my Domain Administrator credentials, UAC would prompt after I click "Install" and I would accept. Prior to installation completion, the client setup prompts to "Start service", and I check that option and then click "Finish".
It was found that the service did NOT actually start and I had to manually start the service in services.msc or run "net start NSClientpp" in a command window as Administrator!


I know that this is NOT specifically a Nagios XI problem, but can anyone provide a way to have the service start when it's supposed to after checking that option, even if UAC is running?? If UAC allows the NSClient++ installer to install, why won't it allow the last part to start the service since it's still part of that install process??

Thanks!

[WillemDH]

Hey PhilG,

You can discuss issues with NSclient++ here: https://www.nsclient.org/forums/forum/nsclient-support/ or post an issue on Michael Medin's GitHub account here: https://github.com/mickem/nscp/issues

Grtz

Willem

[PhilG]

Hey PhilG,

You can discuss issues with NSclient++ here: https://www.nsclient.org/forums/forum/nsclient-support/ or post an issue on Michael Medin's GitHub account here: https://github.com/mickem/nscp/issues

Grtz

Willem

Thank you. I have submitted my question to them and hoping to get a response.

You may lock this post.

[cmerchant]

We'll go ahead and lock this thread. Thanks.