NSClient++ Help (#1) - Can't get the Window sp2 2003 information [SOLVED] (#577) - Message List

Can't get the Window sp2 2003 information [SOLVED]

hi, I have installed NSClient++-0.3.7-Win32.zip in a windows 2003 sp2, and then I started the Nsclient service.

On my nagios server I type "/check_nt -H 172.19.13.118 -p 12489 -v SERVICESTATE -l W3SVC", but the server tell me that "Connection refused could not fetch information from server". 

The nsclient.log(on the Win2003) list that
2010-05-11 10:20:44: debug:NSClient++.cpp:638: NSCLient++ - 0.3.7.493 2009-10-12 Started!
2010-05-11 10:20:44: debug:modules\SysTray\TrayIcon.cpp:53: Failed to load: ChangeWindowMessageFilter aparently we are not on Vista...
2010-05-11 10:21:44: debug:modules\NSCAAgent\NSCAThread.cpp:215: Nothing to report, thus not reporting anything...

But Another win2003's nsclient.log also have such information, but I can get nagios information from the second Win2003 server!

and the two win2003 server have the same nsc.ini What can i do? thanks everyone!

xuyan
05/11/10 05:56:48 (3 years ago)
Tree View Flat View (newer first) Flat View (older first)
  • Message #1754

    When you have connection problem follow the guide under doc/usage/nagios/nsclient. Especially the /test part.

    Michael Medin

    mickem
    05/11/10 06:03:26 (3 years ago)
    • Message #1756

      The problem has been solved. Because my win2003 server doesn't allow to received data from the port of 12489.

      Thanks you very much!

      xuyan
      05/11/10 11:05:28 (3 years ago)
  • Message #1755

    I have followed your suggestion! and I didn't receive any information from the nagios server under the nsclient-test mode. So I think it may be the problem of my win2003's setting.

    Thank you very much!

    xuyan
    05/11/10 10:33:50 (3 years ago)
    • Message #1757

      Thats possible if you have a firewall started. I suggest you turn that off or test on a machine with no fw until you get the hang of it.

      I setup it up on my own xp client while testing. It worked fine.

      When you have disabled the fw you need to make sure that you have configured the ini file correctly.

      When everthing is working it should be easy for you to configure the firewall to allow the traffic.

      vikjon0
      05/11/10 19:30:38 (3 years ago)
      • Message #1758

        Thanks for your suggestion! I didn't start firewall, but the TCP/IP protocol on my win2003 forbid the TCP's 12489 port. I think that maybe the point of the problem. I have modified the setting of TCP/IP, and will restart this win2003 later. After restarting, all would be OK!

        xuyan
        05/12/10 03:24:46 (3 years ago)
Tree View Flat View (newer first) Flat View (older first)

Subscriptions