Kbase P26181: Socket error:connection refused by remote host
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/28/2005 |
|
Status: Unverified
SYMPTOM(s):
Socket error:connection refused by remote host
HTTP 500 Internal server error
FIX:
"Socket Errors"
·"Unable to create socket - the WinProxy server may be to busy". This means that all available sockets on the system are in use. Wait until some of the socket connections are freed or if WinProxy is running on a Windows 95 system consider moving it to a Windows NT system because it has a higher number of sockets.
·"Unable to bind data connection to specified port". WinProxy was unable to listen for a connection on a specific port. This could happen if there is another service already using that port. It can also happen in FTP if there is an error binding the data connection.
·"Unable to set up asynchronous communication". This is an internal TCP/IP error.
·"Incorrectly Formatted URL" - The URL was not formatted correctly.
·"Protocol Not Supported". The requested protocol is not supported, i.e. Gopher enabled in the browser.
"Connection Errors"
·"Unable To Connect To Remote Host" or "Connection Refused by Remote Host". Either the host is not accepting connections or there was a network error (during setup an error in local IP addressing might cause this). WinProxy tried to establish a connection to a server but the server either refused the connection or was not available. This could indicate that the remote server is down, or the name or IP address specified is incorrect, or the appropriate server is not running on the specified machine.
·"Connection Refused. Too many people are already using WinProxy. Try again later." In WinProxy Lite, this is returned to indicate that the simultaneous three user limitation has been reached.
·"Connection refused. You are not authorized to use the specified protocol through WinProxy". If users are configured, then this message indicates that the particular user requesting the connection does not have permission to use the requested protocol. It is also possible that a connection was requested and the required protocol was not required. User configuration is available in WinProxy -> File -> Advanced Properties -> Users. Protocol configuration is available in WinProxy -> File -> Advanced Properties -> Protocols.
Common HTTP Codes
200 · Success: OK
201 · Success: Created
202 · Success: Accepted
203 · Success: Partial Information
204 · Success: No Response
300 · Success: Redirected
301 · Success: Moved
302 · Success: Found
303 · Success: New Method
304 · Success: Not Modified
305 - Use Proxy
400 · Failed: Bad Request
401 · Failed: Unauthorized
402 · Failed: Payment Required
403 · Failed: Forbidden
404 · Failed: Not Found
405 - Method Not Allowed
406 - Not Acceptable
407 - Proxy Authentication Required
408 - Request Time-Out
409 - Conflict
410 - Gone
411 - Length Required
412 - Precondition Failed
413 - Request Entity Too Large
414 - Request-URL Too Large
415 - Unsupported Media Type
500 · Failed: Internal Error
501 · Failed: Not Implemented
502 · Failed: Overloaded Temporarily
503 · Failed: Gateway Timeout
504 - Gateway Time-Out
505 - HTTP Version Not supported