Page 1 of 1
NSClient++ error could not fetch information from server
Posted: Thu Oct 13, 2011 9:18 am
by nagiostool
I'm facing "could not fetch information from server" error when using NSClient++ and giving warning .
In the NSClient Log file its giving as unauthorized access from "172.x.x.x" but the nagios xi server ip is different...
Can anyone help me regarding this ??
Re: NSClient++ error could not fetch information from server
Posted: Thu Oct 13, 2011 11:09 am
by nscott
I think that 172 address is the generic Microsoft "I can't contact the DHCP server" address. Make sure that the Nagios XI server is on the NSClient's list of approved hosts. There are a couple places in the nsclient config that you can specify it at.
Re: NSClient++ error could not fetch information from server
Posted: Mon Feb 13, 2012 5:13 pm
by nagiosadmin42
I was having a similar issue with
Unauthorized access messages in nsclient.log.
When I installed NSClient++ on my Windows remote host, I entered the Allowed Hosts value as a space-separated list, similar to how I configured the
only_from entry in
/etc/xinetd.d/nrpe on Linux. It turns out that the syntax of the
allowed_hosts entry on Windows in NSC.ini is a
comma-separated list. There are comments in NSC.ini describing the supported syntax:
Code: Select all
;# ALLOWED HOST ADDRESSES
; This is a comma-delimited list of IP address of hosts that are allowed to talk to the all daemons.
; If leave this blank anyone can access the deamon remotly (NSClient still requires a valid password).
; The syntax is host or ip/mask so 192.168.0.0/24 will allow anyone on that subnet access
Once I changed to a comma-separated list for
allowed_hosts in NSC.ini and restarted the NSClient++ service, Nagios XI could communicate with the Windows remote host.
Re: NSClient++ error could not fetch information from server
Posted: Mon Feb 13, 2012 10:30 pm
by scottwilkerson
Yep, NSClient++ looks for a comma seperated list.