[Nagiosplug-help] NSClient Failing after a few minutes

[Thomas Stocking]

Thanks, Tony.
I have downloaded and am testing your replacement client. It is working 
well in test, but I do not think it will solve my problem.
I can't use it in this case since the server in question (Win 2K) does 
not use the .NET framework.
It will not have it loaded anytime soon for a lot of reasons. I'm also 
concerned that if this is a major flaw in the existing NSClient, a lot 
of servers will see the service start failing around the world. I'm 
proceeding to try debugging steps, but I'm hoping someone else has 
already hit (and solved?) this issue.   
    Thomas
 

Anthony Montibello wrote:

>Hi Thomas, 
>
>How about trying the NS_Client drop in replacement NC_Net that I have
>been working on.  The new version that will be dated 12/20 v0.17
>should allow for port change.  The only known problems so far is File
>age is not implemented. If your interested go to its home page: 
>www.shatterit.com/NC_Net
>
>I have tested changing ports and it worked.  to change port of NC_Net
>goto the properties of NC_Net in the Windows Services.  make sure the
>service is stoped.  TO the start parameters add: port 12480   and then
>press the start button to start the service.
>the Check_nt password can in a similar way.  Future versions will
>include ability to save the configuration for non default options like
>these.
>
>Hope this Helps,
>Tony
>amontibello at gmail.com
>
>On Sat, 18 Dec 2004 16:59:55 -0800, Thomas Stocking
><tstocking at itgroundwork.com> wrote:
>  
>
>>Hi all,
>>I'm using NSClient 2.01 on several Win 2000 servers. This works fine for
>>most of them, however I am seeing two that exhibit some bad behavior.
>>The service will fail after a few seconds to a few minutes from restart.
>>The event log contains a message about the service "stopping suddenly".
>>
>>These systems were working fine for months. The failure was occasioned
>>by routine maintenance.
>>The SA for these systems applied the latest Microsoft security updates
>>and patches and restarted.
>>
>>I'm using a different port than the default (12480). I had an issue with
>>the default port (1248) as have others, but changing it seems to have
>>fixed things.  I have not seen this problem before. Anyone seen it? I'm
>>afraid Microsoft may have broken this agent, and we need to find a
>>work-around...
>>
>>Is anyone maintaining this now? support.tsmgsoftware.com is off the air...
>>
>>Thomas
>>
>>-------------------------------------------------------
>>SF email is sponsored by - The IT Product Guide
>>Read honest & candid reviews on hundreds of IT Products from real users.
>>Discover which products truly live up to the hype. Start reading now.
>>http://productguide.itmanagersjournal.com/
>>_______________________________________________
>>Nagiosplug-help mailing list
>>Nagiosplug-help at lists.sourceforge.net
>>https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
>>::: Please include plugins version (-v) and OS when reporting any issue.
>>::: Messages without supporting info will risk being sent to /dev/null
>>
>>    
>>