Connection Icq Has Failed System Error Code 10053
Contents |
User Forum List Active Topics Search Who's Online Help Page 1 of 5 1 2 3 4 5 > Topic Options #5771 -
Socket Error 10053 Software Caused Connection Abort
10/01/03 03:00 AM * [10053] Software caused connection abort whiskey Bowl of petunias Registered: what is a socket error 10/01/03 Posts: 2 Greetings,I seem to be getting disconnected alot with 6.03(in status window) * [10053] Software caused connection abort socket error 10054 connection reset by peer Can anyone tell me what might be causing this?I'm on cable and no other services or apps are dropping connect.I have these running almost always, (icq, ftp, usenet download, radmin and email [15 min http://forums.ceruleanstudios.com/archive/index.php/t-92548.html interval]]cheers,whiskeyefnet Top #5772 - 10/01/03 05:24 AM Re: * [10053] Software caused connection abort Watchdog Hoopy frood Registered: 09/12/02 Posts: 2984 Loc: Hill End, NSW, Australia How often does it happen and how long has it happened for? It usually just means that your connection has failed for some reason. _________________________ Induced IRCirc.induced.net Top #5773 - 10/01/03 08:19 AM Re: * [10053] Software caused connection abort Poppy http://forums.mirc.com/ubbthreads.php/topics/5771/all/*_[10053]_Software_caused_conn Hoopy frood Registered: 09/12/02 Posts: 843 Loc: UK This thread might help. _________________________ Never compare yourself to others - they're more screwed up than you think. Top #5774 - 11/01/03 04:53 PM Re: * [10053] Software caused connection abort jaban Pikka bird Registered: 07/01/03 Posts: 16 Alright, I had posted this under "Connection Issues" but here is likely more fitting...Winsock error 10053 occurs randomly under Windows XP Professional when using mIRC version 6.x.Other than that it happens at least once per day, it seems completely random (sometimes it stays connected for 10 minutes, sometimes 15 hours).I have tried using versions 6.01, 6.02, and 6.03, and each have the same problem. I tried running it on different computers running Windows XP Professional, and the same problems occurs on all of these computers. I have asked a few of my friends if they have the same problem, and they do. Using a different server or a different network does not affect the problem.The problem DOES NOT occur with mIRC version 5.9 on Windows XP Professional. The problem DOES NOT occur with mIRC version 6.x on Windows 98. One more note - this error occurs both with and without XP service pack 1 installe
scripting and object-oriented languages on multiple platforms. Currently he is mainly focusing on RESTful (ROA) and Service (SOA) Oriented Architectures, Enterprise Software / Architecture and RESTful Web Services in the http://blog.ronischuetz.com/2007_01_01_archive.html transportation industry. Monday, January 29, 2007 Windows TCP Error Codes (Winsock Error Codes) WSAEACCES(10013)Permission denied. An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST).WSAEADDRINUSE(10048)Address already in use. Only one usage of each socket address (protocol/IP address/port) is normally permitted. This error occurs if an application socket error attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that wasn't closed properly, or one that is still in the process of closing. For server applications that need to bind multiple sockets to the same port number, consider using setsockopt(SO_REUSEADDR). Client applications usually need not call bind at all - connectwill choose an unused port automatically.WSAEADDRNOTAVAIL(10049)Cannot socket error 10053 assign requested address. The requested address is not valid in its context. Normally results from an attempt to bind to an address that is not valid for the local machine, or connect/sendtoan address or port that is not valid for a remote machine (e.g. port 0). WSAEAFNOSUPPORT(10047)Address family not supported by protocol family. An address incompatible with the requested protocol was used. All sockets are created with an associated "address family" (i.e. AF_INET for Internet Protocols) and a generic protocol type (i.e. SOCK_STREAM). This error will be returned if an incorrect protocol is explicitly requested in the socket call, or if an address of the wrong family is used for a socket, e.g. in sendto. WSAEALREADY(10037)Operation already in progress. An operation was attempted on a non-blocking socket that already had an operation in progress - i.e. calling connecta second time on a non-blocking socket that is already connecting, or canceling an asynchronous request (WSAAsyncGetXbyY) that has already been canceled or completed. WSAECONNABORTED(10053)Software caused connection abort. An established connection was aborted by the software in your host machine, possibly due to a data transmission timeout or protocol error. WSAECONNREFUSED(10061)Connection refused. No connection could be made because the target machine actively refused it. Thi
be down. Please try the request again. Your cache administrator is webmaster. Generated Wed, 05 Oct 2016 02:02:16 GMT by s_hv902 (squid/3.5.20)