[RESOLVE] CRITICAL - socket timeout on one server.. but..

[Nemo-rec]

Hello all,
i don't understand ....

i have 2 nagios servers.
the old Nagios, Ver. 3.2.1 - March 09, 2010
the new nagios, Ver. 4.0.8 - August 12, 2014 (that i configuring since 15/20 days to replace the older, yes it's long but i reconfigure all the config !!)

almost everything works fine, almost .... just one problem..

root@Superviseur:/usr/local/nagios/libexec# ./check_nt -H XXX.XXX.3.249 -v UPTIME -p 12489 -s XXXXXXXXX
CRITICAL - socket timeout after 10 seconds

or, even if i try to grow up the delay

root@Superviseur:/usr/local/nagios/libexec# ./check_nt -H XXX.XXX.3.249 -v UPTIME -p 12489 -s XXXXXXXXX -t 60
CRITICAL - socket timeout after 60 seconds

but ...if i check another servers, even on different sub-mask

root@Superviseur:/usr/local/nagios/libexec# ./check_nt -H XXX.XXX.3.3 -v UPTIME -p 12489 -s XXXXXXXXX
System Uptime - 5 day(s) 23 hour(s) 10 minute(s)

root@Superviseur:/usr/local/nagios/libexec# ./check_nt -H XXX.XXX.2.5 -v UPTIME -p 12489 -s XXXXXXXXX
System Uptime - 11 day(s) 7 hour(s) 29 minute(s)

and, if i check the same server on the older nagios server...

[root@nagios:/usr/local/nagios/libexec]$ ./check_nt -H XXX.XXX.3.249 -v UPTIME -p 12489 -s XXXXXXXXX
System Uptime - 5 day(s) 23 hour(s) 31 minute(s)

=>> The response is immediate


the config of the NSC.ini is the same on all my windows servers
use_file=1
allowed_hosts=XXX.XXX.2.18,XXX.XXX.2.16
password=XXXXXXXXX

the result of
nmap -p 5666,12489 XXX.XXX.3.249

Starting Nmap 6.00 ( http://nmap.org ) at 2015-04-27 11:39 CEST
Nmap scan report for siletd.NNNNNN.NNNNN (XXX.XXX.3.249)
Host is up (0.030s latency).
PORT STATE SERVICE
5666/tcp filtered nrpe
12489/tcp filtered unknown

Nmap done: 1 IP address (1 host up) scanned in 1.44 seconds

for both "nagios" & "superviseur" servers....



please, any idea ??

[jdalrymple]

Check your windows firewall. That port needs to be open, not filtered.

Code: Select all

[jdalrymple@localhost libexec]$ nmap -p 12489 winhost

Starting Nmap 5.51 ( http://nmap.org ) at 2015-04-27 13:13 CDT
Nmap scan report for winhost
Host is up (0.0053s latency).
PORT      STATE SERVICE
12489/tcp open  unknown

Nmap done: 1 IP address (1 host up) scanned in 1.25 seconds
[jdalrymple@localhost libexec]$ ./check_nt -H winhost -v UPTIME -p 12489 -s secret
System Uptime - 3 day(s) 21 hour(s) 14 minute(s) |uptime=5594

[Nemo-rec]

thanks, shame on me, i didn't think about it.
this is the only one that has Firewall configured with the maximum severity.

it works.
thanks.

[lmiltchev]

I am glad your issue was resolved! I am locking the topic.