[10053] Il Software ha causato l'aborto della connessione

[Mi fuma il pc]

Salve!

Scusate se apro un nuovo topic, ho provato su "Cerca" ma non ho trovato nulla a riguardo

Quando apro un script dopo circa 5 minuti mi esce la maledetta scritta

*** [10053] Il Software ha causato l'aborto della connessione.

Il primo momento pensavo che il disturbo derivasse dal sistema operativo
( Xp Home ) ma poi ho provato con "Xp professional" e con Windows 2000" ma nulla da fare

Un enorme grazie a chi mi sa dire cosa fare

[Dylan666]

http://www.mondoirc.net/forum/topic.asp?TOPIC_ID=928

http://support.microsoft.com/kb/q204594/

[Mi fuma il pc]

Dylan666 6 grande

Ho risolto il problema cercando sul sito che mi hai dato ho trovato, scaricato e installato il Winfix.

Almeno x il momento la connessione è stabile, lo script è acceso da circa 4 ore senza problemi!

Ancora 1001 grazie Dylan666. 6 un mito ( nulla da togliere a tutti gl'altri)

[Dylan666]

Riporto i passaggi salienti del mio link:

http://www.sockets.com/

WSAECONNABORTED (10053) Software caused connection abort.

Berkeley description: A connection abort was caused internal to your host machine. The software caused a connection abort because there is no space on the socket's queue and the socket cannot receive further connections.

WinSock description: Partly the same as Berkeley. The error can occur when the local network system aborts a connection. This would occur if WinSock aborts an established connection after data retransmission fails (receiver never acknowledges data sent on a datastream socket).

TCP/IP scenario: A connection will timeout if the local system doesn't receive an (ACK)nowledgement for data sent. It would also timeout if a (FIN)ish TCP packet is not ACK'd (and even if the FIN is ACK'd, it will eventually timeout if a FIN is not returned).

User suggestions: There are a number of things to check, that might help to identify why the failure occurred. Basically, you want to identify where the problem occurred.

Ping the remote host you were connected to. If it doesn't respond, it might be off-line or there may be a network problem along the way. If it does respond, then this problem might have been a transient one (so you can reconnect now), or the server application you were connected to might have terminated (so you might not be able to connect again).
Ping a local host to verify that your local network is still functioning (if on a serial connection, see next step)
Ping your local router address. If you're on a serial connection, your local router is the IP address of the host you initially logged onto with SLIP or PPP.
Ping a host on the same subnet as the host you were connected to (if you know one). This will verify that the destination network is functioning.
Try a "traceroute" to the host you were connected to. This won't reveal too much unless you know the router addresses at the remote end, but it might help to identify if the problem is somewhere along the way.
WinSock functions: recv(), recvfrom(), sendto(), FD_CLOSE

Additional functions: send() can also fail with WSAECONNABORTED. Any function that takes a socket as an input parameter--except close socket()--could potentially fail with this error.

fatto come hai detto tu e nn ho risolto nulla....ho risolto in un'altra maniera ...ho scaricato Winfix per xp ho rifatto tutto il procedimento ....ipv6 install,installare la scheda loopback creare il tunnel ed il gioko è fatto...

http://www.spychecker.com/program/winsockxpfix.html