Socket timeout after 10 seconds

[deepakitkar]

I am facing this issue lately with one of the windows server. I tried reinstalling the client but no success. Any idea

CPU Usage Critical 8d 2h 26m 17s 5/5 2013-05-03 02:36:49 CRITICAL - Socket timeout after 10 seconds
Drive C: Disk Usage Critical 8d 2h 26m 5s 5/5 2013-05-03 02:36:49 CRITICAL - Socket timeout after 10 seconds
Logon Errors Critical 8d 2h 25m 53s 5/5 2013-05-03 02:38:37 CRITICAL - Socket timeout after 10 seconds
Memory Usage Critical 8d 2h 25m 41s 5/5 2013-05-03 02:39:16 CRITICAL - Socket timeout after 10 seconds

-----------------------------------------------
Here is the result of NMAP:
nmap <my ip> -p 12489

Starting Nmap 4.11 ( http://www.insecure.org/nmap/ ) at 2013-05-03 04:16 EDT
Interesting ports on <my ip>:
PORT STATE SERVICE
12489/tcp filtered unknown

Nmap finished: 1 IP address (1 host up) scanned in 0.333 seconds
-----------------------------------------------

Any idea to get away with this issue?

Thanks!

[sreinhardt]

Filtered could mean that this port is not actually open, either via windows firewall, a proxy or transparent firewall, or that the service is not running. Can you verify that you have created a windows firewall rule to allow 12489 incoming? Also that there is not a firewall, or that it has ports opened to allow communication? If these are not the case, you can also use the -t flag with check_nt to extend the default timeout. -t 30 or -t 60 is fairly common.

[deepakitkar]

@sreinhardt,

This didn't help. Any other suggestions?

[scottwilkerson]

Can you confirm that NSClient++ service is running on the remote system and there is NO firewall between these systems?

[deepakitkar]

After comparing the results with 2 different server on different ip, finally figured out that this server hasn't been allowed port 12489 access from Nagios. After allowing the port, everything seems working.

Thanks all!