topic Re: ECONNREFUSED in Operating System - HP-UX

ECONNREFUSED

Tom Dawson — Wed, 20 Mar 2002 20:41:58 GMT

Hi,

I have a D330 running v11.11. I've installed a vendors sw application that connects via the internet to their server to upload transaction data.

Their app uses ssl. So I have verified that port 443 is open on our firewall.

When I test their app, it generates the following in their log file:

ECONNREFUSED - Connection refused.
Connection failed -- error code -239.

The error is generated so fast that I'm fairly certain that nothing has actually left my D330.

I looked in /usr/include/sys/errno.h and found this:

# define ECONNREFUSED 239 /* Connection refused */

I'm confused that this entry is commented out.

Can someone point me to a document that might explain what is involved in a ECONNREFUSED error?

TIA,
Tom

Re: ECONNREFUSED

Sandip Ghosh — Wed, 20 Mar 2002 20:58:05 GMT

You can have a look over here.

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90701/B2355-90701_top.html&con=/hpux/onlinedocs/B2355-90701/00/00/79-con.html&toc=/hpux/onlinedocs/B2355-90701/00/00/79-toc.html&searchterms=ECONNREFUSED&queryid=20020320-130058

Sandip

Re: ECONNREFUSED

Steven Gillard_2 — Wed, 20 Mar 2002 21:05:46 GMT

A connection refused means that the remote system is not listening on the port you're trying to establish a connection with. From a TCP point of view this is the error you'll get when the remote system responds to a SYN with a RST.

So, whatever service you're trying to connect to is not running on the remote system. I doubt its a firewall issue - if the firewall was dropping the packets you would have got a timeout, not a connection refused.

Regards,
Steve

Re: ECONNREFUSED

rick jones — Wed, 20 Mar 2002 23:50:02 GMT

as has been pointed-out, an ECONNREFUSED will happen when the initial SYN segment (triggered when you call connect()) receives a RST segment in response rather than a SYN|ACK.

indeed, a firewall could in theory (if not likely in practice) be configured to return a RST.

it is also possible that the remote application is not running and listening on that port number.

if the remote app is running under a windows variant, MS also will return an RST (bogusly in most IETF types opinions :) if the apps listen queue is full.