CRITICAL - Socket timeout after 30seconds

[veenm]

I have installed the nagios agent version 0.3.9 on Windows XP . But i am not getting the service check results. When i run the command from the nagios it gives "CRITICAL - Socket timeout after 10 seconds"

[root@xxxx libexec]# ./check_nt -H aaa -p 12489 -v USEDDISKSPACE -d SHOWALL -l c
CRITICAL - Socket timeout after 30 seconds

Port is open on client side.
C:\Program Files\NSClient++>netstat -a | find "LISTENING"
TCP BC757213-PC:5666 xxxx LISTENING
TCP BC757213-PC:12489 xxxx LISTENING
I have tried all the option to troubleshoot which are available in net but no success.

when i tested the nsclient in the tested mode i got the below error.

e \Socket.h(691) bind failed: 10048: Only one usage of each socket address (prot
ocol/network address/port) is normally permitted.
e \Socket.h(722) Socket did not start properly, we will now do nothing...

in reinstalled the agent , rebooted the pc , everything.
Please assist me in resolving the issue.

[abrist]

You need to specify your password in the check:

Code: Select all

./check_nt -H aaa -p 12489 -s "<password>" -v USEDDISKSPACE -d SHOWALL -l c

[veenm]

i checked with password also , but it did not worked

[abrist]

Can you run an nmap from the nagios server?

Code: Select all

nmap aaa -p 12489

[veenm]

I got below out put and nagios server is able to access the client

[root@xxxlibexec]# nmap aaa -p 12489

Starting Nmap 6.25 ( http://nmap.org ) at 2013-09-26 09:15 CST
Nmap scan report for 10.17.44.115 (10.17.44.115)
Host is up (0.083s latency).
PORT STATE SERVICE
12489/tcp filtered unknown

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

[abrist]

12489/tcp filtered unknown

Looks like the port is not open. "filtered" usually implies that a network device is blocking access to that port. It could be a software firewall, but my bet is on a networking device. Is there a router or firewall between the nagios server and the windows host?

[veenm]

ya there is a firewall.

[slansing]

So is port 12489 open on the firewall??