IRC socket

Answer/Solution: 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: 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).


Alejandro Curquejo
Microsoft MVP
Windows XP Shell/User
Microsoft Newsgroups
Andalucia ES
MVP Program: http://mvp.support.microsoft.com/
DTS-L.org: http://dts-l.org/index.html
Perfil: http://tinyurl.com/7cfp3


"fermu [MVP Windows]" wrote in message
news:%

Víctor wrote:

cuando intento acceder a IRC me da este error:
IRC socket: Failed to connect - Error 10053: Se ha anulado una conexión
establecida por el software en su equipo host..

Es un error genérico de las WinSock, es un error de cara al equipo
cliente, (tu equipo) y normalmente significa que se ha agotado el tiempo
de espera intentando conectar al servidor, pero esto puede suceder por
varios motivos, entre ellos winsock corruptas, si tienes winxp sp2
teclea este comando y prueba suerte:

netsh winsock reset catalog



Saludos
MS MVP Windows - Shell/User
Fermu's Website - http://www.fermu.com
Fermu's Forum - http://fermu.notlong.com/

Bueno también podría ser una corrupción del WinSock, ¿no?... digamos que
como posibilidad.

Alezito [MS MVP] wrote:

Answer/Solution: 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: 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).

¿Problemas con Windows Update?
http://www.fermu.com/content/section/5/37/lang,es/
Windows Update Issues?
http://www.fermu.com/content/section/5/37/lang,us/

Si, si, solo complementaba informacion, porque creo que no es facil centrar
el problema.

Alejandro Curquejo
Microsoft MVP
Windows XP Shell/User
Microsoft Newsgroups
Andalucia ES
MVP Program: http://mvp.support.microsoft.com/
DTS-L.org: http://dts-l.org/index.html
Perfil: http://tinyurl.com/7cfp3


"José Gallardo" wrote in message
news:

Bueno también podría ser una corrupción del WinSock, ¿no?... digamos que
como posibilidad.

Alezito [MS MVP] wrote:

Answer/Solution: 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: 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).

¿Problemas con Windows Update?
http://www.fermu.com/content/section/5/37/lang,es/
Windows Update Issues?
http://www.fermu.com/content/section/5/37/lang,us/

Funcionó, gracias por vuestro interés

"Alezito [MS MVP]" escribió:

Si, si, solo complementaba informacion, porque creo que no es facil centrar
el problema.

Alejandro Curquejo
Microsoft MVP
Windows XP Shell/User
Microsoft Newsgroups
Andalucia ES
MVP Program: http://mvp.support.microsoft.com/
DTS-L.org: http://dts-l.org/index.html
Perfil: http://tinyurl.com/7cfp3


"José Gallardo" wrote in message
news:
> Bueno también podría ser una corrupción del WinSock, ¿no?... digamos que
> como posibilidad.
>
> Alezito [MS MVP] wrote:
>> Answer/Solution: 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: 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).
>>
>>
>
> ¿Problemas con Windows Update?
> http://www.fermu.com/content/section/5/37/lang,es/
> Windows Update Issues?
> http://www.fermu.com/content/section/5/37/lang,us/