The old NSClient is notorious for not reporting problems correctly.
Usually, when this happens, I find the issue is that the TCP port has
been stolen by another application. Exchange is frequently guilty of
this as it starts getting temporary port numbers from 1024 upwards and
quickly takes the NSclient port 1248. Try moving nsclient to a much
higher port number, or else get it to start before any other apps on the
box.
You can test this by using netstat to see if port tcp/1248 is in use,
and if so, by what.
netstat -a -p TCP -b -n
This might take a little time to run though. Look for lines with :1248
in the first column.
Steve
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sudhir
Damle
I have installed NSClient 2.0.1.0 on Windows 2000 server. Client was
working Good till I rebooted the server.
Now whenever I start ' Nagios Agent' service, it gets started,
application event viewer says 'NSClient is now responding to queries'
but service simply stops after that. No error in event viewer.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
