Connection refused

[Kevin Keane]

It may well be correct, but is a completely different setup! You have an 
SSH tunnel; that's a rather critical piece of information. You have an 
SSH tunnel from the Windows machine to somewhere else, instead of having 
an NSClient++.

Maybe you meant to do a remote port forwarding and instead set up local 
port forwarding.

Surajit Mukherjee wrote:
> Hi Kevin,
>
> The output netstat -anb looks like this.
>
> TCP    0.0.0.0:****   0.0.0.0:**      ESTABLISHED     ****
>  [putty.exe]
>
>
> Where in left 0.0.0.0:**** is my windows server along with port and the
> right is the Linux server along with port. Is it not correct?
>
> Surajit 
>  
>
> -----Original Message-----
> From: Kevin Keane [mailto:subscription at kkeane.com] 
> Sent: Friday, May 08, 2009 1:56 PM
> Cc: Nagios User list
> Subject: Re: [Nagios-users] Connection refused
>
> What connection, exactly, do you show as "established" with netstat -an?
>
> It can't really be the one you are talking about, because that never 
> connected.
>
> In any case, you would want to look for LISTENING rather than 
> ESTABLISHED in the output for netstat -an. The local address on the left
>
> should say something like 0.0.0.0:xxxx (where xxxx is the port number). 
> If it says 127.0.0.1 then NSClient++ is not listening on the Ethernet
> port.
>
> If you don't see an entry that listens on the correct port, then 
> double-check that NSClient++ is running.
>
> If you do see an entry to listen on the correct port, try running nestat
>
> -anb . This will tell you which program is actually doing the listening.
>
> If it isn't NSClient++, you found your culprit. That's not likely,
> though.
>
> If netstat -anb shows NSClient++ as listening correctly, you almost 
> certainly have a firewall issue.
>
> Surajit Mukherjee wrote:
>   
>> Andy,
>>
>> I am unable to telnet to the port from the Nagios server.
>>
>> I checked netstat -an and the connection is established. I am able to
>> telnet from windows server to the Linux server.
>>
>> Surajit 
>>  
>> -----Original Message-----
>> From: Andy Shellam [mailto:andy-lists at networkmail.eu] 
>> Sent: Friday, May 08, 2009 12:03 PM
>> To: Surajit Mukherjee
>> Cc: Nagios User list
>> Subject: Re: [Nagios-users] Connection refused
>>
>> Surajit,
>>
>> Is the service actually running on that server?  Can you telnet to the
>>     
>
>   
>> NSClient++ port manually?
>>
>> Regards,
>> Andy
>>
>> Surajit Mukherjee wrote:
>>   
>>     
>>> I am getting "Connection refused" status information on a Windows
>>>       
> 2003
>   
>>> Server that is using NSClient++.  Out of the 7 Windows server I have
>>>     
>>>       
>> in
>>   
>>     
>>> Nagios 3.0.6, this is the only server giving me that error
>>>
>>> ** **
>>>
>>> **Cheers,**
>>>
>>> **Surajit**
>>>     
>>>       


-- 
Kevin Keane
Owner
The NetTech
Find the Uncommon: Expert Solutions for a Network You Never Have to Think About

Office: 866-642-7116
http://www.4nettech.com

This e-mail and attachments, if any, may contain confidential and/or proprietary information. Please be advised that the unauthorized use or disclosure of the information is strictly prohibited. The information herein is intended only for use by the intended recipient(s) named above. If you have received this transmission in error, please notify the sender immediately and permanently delete the e-mail and any copies, printouts or attachments thereof.


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
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