Hi Experts,
We are trying to add Windows server in Nagios monitoring.
We have opened following firewalls:
1. Nagios to Windows server : 135, 445
2. Windows node to Nagios : 1024 to 65535(DCOM range ports).
While executing the check_wmi_plus.pl command, we are getting time out error. Please find the below for reference:
/usr/local/nagios/libexec/check_wmi_plus.pl -H 10.10.192.158 -u 'domain\user' -p 'password' -m checkcpu -w '80' -c '90' -d
Command Line (v1.6): /usr/local/nagios/libexec/check_wmi_plus.pl -H 10.10.192.158 -u USER -p PASS -m checkcpu -w 80 -c 90 -d
Base Dir: /usr/local/nagios/libexec
Conf File Dir: /usr/local/nagios/libexec
Loaded Conf File /usr/local/nagios/libexec/check_wmi_plus.conf
Starting Keep State Mode
STATE FILE: /tmp/cwpss_checkcpu__1010192158___.state
Round #1 of 1
QUERY: /usr/bin/wmic '-U' 'USER%PASS' '--namespace' 'root/cimv2' '//10.10.192.158' 'select PercentProcessorTime,Timestamp_Sys100NS from Win32_PerfRawData_PerfOS_Processor where Name="_Total"'
UNKNOWN - Plugin Timed out (15 sec). There are multiple possible reasons for this, some of them include - The host 10.10.192.158 might just be really busy, it might not even be running Windows.
We tried increasing the timeout value to 120 step by step from 30..and we still are getting the same error.
When we checked with Network team to see any firewall port is getting blocked, we received an information that TCP port 6007 is getting blocked.
We need to know what is the significance of TCP port 6007. We could not find any information the same in any Nagios document.
Also, need to know what else could be the reason for command failing with timeout.
The user name and password are working fine and we could connect to the server via RDP using the same credentials.
Please help.
Regards
Vishal Dhote
TCP Port 6007
Re: TCP Port 6007
Port 6007 is RPC.
WMI connects over 135, 445 but the server itself replies with the port that it should use for further communication.
See here:
https://support.microsoft.com/en-us/hel ... -firewalls
WMI connects over 135, 445 but the server itself replies with the port that it should use for further communication.
See here:
https://support.microsoft.com/en-us/hel ... -firewalls