Please help with Exchange issues

[benningtonr]

I am getting the following errors, i uninstalled and re installed the nsclient over the weekend, that did not help.
All other services are reporting fine,



Exchange 2007 Exchange Core Services Critical 1d 10h 57m 6s 5/5 2012-07-02 08:08:07 CRITICAL - Socket timeout after 10 seconds
Exchange Web Services Critical 1d 10h 57m 47s 5/5 2012-07-02 08:10:02 CRITICAL - Socket timeout after 10 seconds
Messages Pending Routing Critical 1d 10h 58m 26s 5/5 2012-07-02 08:11:09 CRITICAL - Socket timeout after 10 seconds
Remote Queue Length Critical 1d 10h 58m 30s 5/5 2012-07-02 08:07:50 CRITICAL - Socket timeout after 10 seconds

[scottwilkerson]

Make sure your firewall is allowing connection to the new nsclient++ on 12489

[benningtonr]

local firewall on exchange is off,
How do I check on the nagios machine?

[scottwilkerson]

I would check your INI file in the NSClient++ setup and make sure that it has your XI server as allowed and the same password. Also make sure the service is running as well as restart the service if you make changes to the INI.

Can you also run the following from your XI console

Code: Select all

cd /usr/local/nagios/libexec
./check_nt -H <REMOTE_IP_ADDRESS> -s <PASSWORD_ON_REMOTE> -p 12489 -v UPTIME

[benningtonr]

CRITICAL - Socket timeout after 10 seconds

still getting same thing

[scottwilkerson]

Did you verify NSClient++ is running? And...

I would check your INI file in the NSClient++ setup and make sure that it has your XI server as allowed and the same password.

[lmiltchev]

On your nagios server run in terminal the following commands and show us the output:

Code: Select all

nc -zv <windows_machine_IP> 12489
telnet <windows_machine_IP> 12489

[benningtonr]

[root@nagios libexec]# nc -zv 192.168.99.14 12489
nc: connect to 192.168.99.14 port 12489 (tcp) failed: Connection refused


[root@nagios libexec]# telnet 192.168.99.14 12489
Trying 192.168.99.14...
telnet: connect to address 192.168.99.14: Connection refused

[benningtonr]

I checked INI file, it had correct password and ip address

[scottwilkerson]

Did you verify NSClient++ service is running?