Why do I get connection refused when the server is not running?
Answer Posted / chaitanya
The connect() call will only block while it is waiting to establish a connection. When there is no server waiting at the other end, it gets notified that the connection can not be established, and gives up with the error message you see. This is a good thing, since if it were not the case clients might wait for ever for a service which just doesn't exist. Users would think that they were only waiting for the connection to be established, and then after a while give up, muttering something about crummy software under their breath.
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
What is a socket file?
What is a socket api?
Why does it take so long to detect that the peer died?
system choose one for me on the connect() call? Should I bind() a port number in my client program, or let the?
What's better 6pt or 12pt sockets?
What's the difference between a socket and a port?
What is the difference between SO_REUSEADDR and SO_REUSEPORT?
How can I set the timeout for the connect() system call?
How can I write a multi-homed server?
Can multiple sockets use the same port?
What does af mean in sockets?
Where is the socket located?
How can I tell when a socket is closed on the other end?
Is socket a hardware or software?
How do unix sockets work?