Hi,
thanks to those who replied, the issue is now resolved.
I had 2 clients configured on the Nagios server with the same IP, as
soon as I changed those IPs on the server side to invented IPs that
were different everything started to work as expected,
cheers Andy.
--
On 02/12/11 18:14, a.sm...@ukgrid.net wrote:
>
> Hi,
>
> in the case where I want to monitor several servers in a remote office
> where all outbound traffic from that office originates from a single
> IP (NAT) is there any way I can monitor those with Nagios without
> putting a Nagios server in
On 3 December 2011 17:46, wrote:
> ok great if its possible, however I did try setting this up and it
> didnt seem to work.
> I am using the NSClient++ on Windows servers, and under the NSCA
> section I have defined what is described as "LOCAL HOST NAME"
> correctly on each client. However when
Quoting Jim Avery:
> The send_nsca transmission identifies the host to Nagios so it won't
matter if the address is NATted.
Hi Jim,
ok great if its possible, however I did try setting this up and it
didnt seem to work.
I am using the NSClient++ on Windows servers, and under the NSCA
sectio
On 2 December 2011 18:14, wrote:
> Hi,
>
> in the case where I want to monitor several servers in a remote office where
> all outbound traffic from that office originates from a single IP (NAT) is
> there any way I can monitor those with Nagios without putting a Nagios
> server in the remote offi
Hi,
in the case where I want to monitor several servers in a remote office where
all outbound traffic from that office originates from a single IP (NAT) is
there any way I can monitor those with Nagios without putting a Nagios server
in the remote office?
On the face of it it would seem impossi
