NSClient++: Connection Refused, again and again, with default config

[Michael Medin]

Best way to debug this is:
1, runt: NSClient++ /test (after stopping the service) and see what happends.

2, enable debug logging and check the nsc.log file.


// Michael Medin

> Hi people of the world :P
>
> I'm just running the NSclient on a Windows machine. I got the default
> configuration of the NSC.ini but I have an error in the nagios:
> Connection refused
> I modified the NSC.ini to run the client on the 12489 port, and I add the
> IP
> of the nagios server on allowed host.
> I have no information about the client version, the cpu or some
> information
> in the nagios.
> I run a netstat in the windows machine and I get the listening port at
> 12489
> but when I try to connect from telnet on the linux (nagios) machine
> I've got a "Connection closed by foreign host."
> I scan the machine with the nmap. It don't show the 12489 open of
> filtered.
>
> What can be wrong?
> In the Windows machine there are no firewall.
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword_______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> 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



------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
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