Connection Refused Windows Agent

[scater]

Just installed nagios using vmware OVF template. Nagios server appears to be running fine. Installed NSClient++ on Win2008 - took all the defaults (made sure to input same password). While the ping service works, the CPU Usage, Drive C: Disk Usage, Memory Usage and Uptime are all reflecting a status of "Connection refused".

The firewall on the WIN2008 server is Off.

All the services monitored on the localhost are working fine.. Any ideas?

[abrist]

Lets try a few things on the XI server:

Code: Select all

nmap <windows server ip> -p 12489
/usr/local/nagios/libexec/check_nt -H <windows server ip> -p 12489 -v CLIENTVERSION -s <password>

[scater]

Thanks for the response - while waiting looked at the FW on the WIN2008 box and it wasn't off - I opened port 5666 and now the response I am getting for all (except ping) win services is:

CRITICAL - Socket Timeout after 10 seconds

Per Your request :
nmap returned
Host is up, PORT 12489/tcp STATE Filtered SERVICE Unknown
nmap done: 1 IP address (1 host up) scanned in 0.34 seconds

Check_nt now returns CRITICAL - Socket timeout after 10 seconds

Do I need to also open port 12489?

And thanks for the response

[abrist]

Yes, port 12489 must be open on the windows server and reachable by the XI server (for check_nt and port 5666 for nrpe).

[slansing]

Do you have the correct IP address of the XI server added in the NSClient++ NSC.ini file? Port 12489 is the port used by check_nt, which is another option for actively checking against NSClient++ and is the basic command used in the Windows Desktop/Server monitoring wizards.

[scater]

Ifound an ini file named NSC.ini - I found the XI server IP address and password - they are correct.

I uncommented the ports 5666 and 12489 that are referenced in the file and I an still getting the same results of the Socket Time out error after 10 seconds

Nmap for port 5666 returns SERVICE nrpe
Nmap for port 12489 returns SERVICE unknown

Hopefully this is what you were looking for - Anything else I can check

[abrist]

If you nmap those ports, are they now open (*un*filtered)?

[scater]

It indicates they are both filtered - does this mean the Win2008 firewall is not properly configured?

[slansing]

This is a possibility, do you have another program on the server which could be filtering ports? Do you have a firewall between the windows server and the Nagios server other than the Windows firewall?

[scater]

So I gather the objective is to get nmap to reflect that the ports are unfiltered- Is that correct? When I use nmap for know ports (i.e. 21, 80) the STATE is filtered..

I have no other firewall in the server - I tried disabling ESET, but that did change anything.