Page 1 of 1

Windows Monitoring over NAT issues

Posted: Fri Jan 22, 2021 10:21 am
by kkuznetsov
Windows Server is on Azure environment. Nagios is on LAN and can reach the monitored server over NAT.
We cannot deploy NCPA via "Manage Deployed Agents > + Add Agent" page as it hangs.
Also, we cannot validate NCPA with "https://[IP address]:5693" web page, as it shows blank page.

SSH from Nagios server is able to run "check_icmp" successfully:
[root@server libexec]# ./check_icmp -H <IP address> -w 3000.0,80% -c 5000.0,100% -p 5
OK - <IP address> rta 4.906ms lost 0%|rta=4.906ms;3000.000;5000.000;0; pl=0%;80;100;0;100 rtmax=7.725ms;;;; rtmin=3.974ms;;;;


but returns an error for "check_ncpa.py":
[root@server libexec]# ./check_ncpa.py -H <IP address> -t 'token' -P 5693 -M cpu/percent -w '80' -c '100' -q 'aggregate=avg'
UNKNOWN: An error occured connecting to API. (Connection error: '[Errno 104] Connection reset by peer')


Please explain what is the problem, and advise how to resolve it.
Thank you.

Re: Windows Monitoring over NAT issues

Posted: Fri Jan 22, 2021 4:24 pm
by kkuznetsov
So, we found the issue source. That was a firewall configuration on Azure site.
After a customer adjusted it, Nagios started communicating with NCPA properly.

Re: Windows Monitoring over NAT issues

Posted: Fri Jan 22, 2021 4:34 pm
by benjaminsmith
Hi,
So, we found the issue source. That was a firewall configuration on Azure site.
After a customer adjusted it, Nagios started communicating with NCPA properly.
Excellent! Glad you got it solved.

We'll go ahead and close this thread, but feel free to open another if you have any new questions.

Benjamin