Nagios Support Forum

i am getting Critical
CRITICAL - Socket timeout after 10 seconds
after installing window Client ns++
this is pretty default config
password has been verified

1) Can you post the full check command which produces this error?

NOTE: The NSClient++ agent can use either check_nt (listening on port 12489) and check_nrpe (port 5666). You will need to manually open those ports on any Firewalls, the install script will not do this for you.

2) Once you know what specific port the agent is listening on, try running an nmap scan against the Win2012 server from the nagios server, and post the output:
nmap <Win Server IP add> -p <12489 or 5666>

this is the output of test after adding ports to firewall
Starting Nmap 6.47 ( http://nmap.org ) at 2016-04-25 16:23 CDT
Nmap scan report for 172.40.1.2
Host is up (0.00066s latency).
PORT STATE SERVICE
12489/tcp filtered unknown
MAC Address: 00:15:5D:02:07:0B (Microsoft)

Nmap done: 1 IP address (1 host up) scanned in 0.64 seconds
[root@nagios ~]# nmap 172.40.1.2 -p 5666

Starting Nmap 6.47 ( http://nmap.org ) at 2016-04-25 16:23 CDT
Nmap scan report for 172.40.1.2
Host is up (0.00077s latency).
PORT STATE SERVICE
5666/tcp filtered nrpe
MAC Address: 00:15:5D:02:07:0B (Microsoft)

Nmap done: 1 IP address (1 host up) scanned in 0.45 seconds
still showing errors on service detial after recheck

Still a FW blocking this traffic, based on the "filtered" portion of the nmap output.

filtered - Nmap cannot determine whether the port is open because packet filtering prevents its probes from reaching the port. The filtering could be from a dedicated firewall device, router rules, or host-based firewall software

https://nmap.org/book/man-port-scanning-basics.html

I'd re-check your FW settings and anything else in the path between Nagios <--> Win Server.
Also, it would be helpful if you posted the full check command as requested earlier, thanks

here is the command used
COMMAND: /usr/local/nagios/libexec/check_nt -H 172.40.1.2 -s "password1" -p 12489 -v CPULOAD -l 5,80,90
OUTPUT: CRITICAL - Socket timeout after 10 seconds

As @bwallace mentioned - there is a firewall on which is why it's timing out. You'll need to allow ports 12489 and 5666 either on the Windows server, or the firewall that is between the Nagios server and the windows machine.