Nagios Support Forum

Posted: **Thu Jul 31, 2014 2:56 pm**

Hi.
We have dozens of windows virtual servers monitored via NSClient + +
Only in one server following this message appears with great frequency: CRITICAL - Socket timeout after 10 seconds
I've reinstalled the NSClient + + and apparently the server has no connectivity problem

How can we debug and solve this problem?

Best Regards

Tcp

Posted: **Fri Aug 01, 2014 11:07 am**

How long has this windows system been up and running? There is a known bug with windows network stack if the system is up for an extended period of time. Other things you should start with, let's make sure the port is open first.

Code: Select all

nmap -p 5666,12489 [windows hostname\ip]

Posted: **Mon Aug 04, 2014 12:42 pm**

The server is up for 8 days

nmap results below

Starting Nmap 5.51 ( http://nmap.org ) at 2014-08-04 14:39 BRT
Nmap scan report for XXXXX (XXX.XXX.X.XXX)
Host is up (0.00038s latency).
PORT STATE SERVICE
5666/tcp filtered nrpe
12489/tcp filtered unknown
MAC Address: XXXXXXXXXXX (Unknown)

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

Posted: **Mon Aug 04, 2014 1:32 pm**

Both ports that you need open (12489 and 5666) are filtered...

5666/tcp filtered nrpe
12489/tcp filtered unknown

You will need to modify your firewall rules and open these ports.

Nagios Support Forum

CRITICAL - Socket timeout after 10 seconds

CRITICAL - Socket timeout after 10 seconds

Re: CRITICAL - Socket timeout after 10 seconds

Re: CRITICAL - Socket timeout after 10 seconds

Re: CRITICAL - Socket timeout after 10 seconds