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
Why does the sockets buffer fill up sooner than expected?
How do unix sockets work?
Where is the socket located?
What is a socket api?
What is difference between socket () and serversocket () class?
How to find other end of unix socket connection?
Is there any advantage to handling the signal, rather than just ignoring it and checking for the EPIPE error? Are there any useful parameters passed to the signal catching function?
Are sockets files?
What are the types of sockets?
What is the purpose of socket?
Why do I get EPROTO from read()?
system choose one for me on the connect() call? Should I bind() a port number in my client program, or let the?
What is sae socket?
What is the difference between read() and recv()?
How does unix socket work?