[10053] has been a steady nemesis for me too.
*) Generally only affects mIRC - that is, ICQ, actively loading sites, downloads, etc, all remain in operation (Except in cases where the entire 'net connection goes south, which is identified by EVERYTHING dying.)
*) Has occured when AFK from machine. When in another CPU intensive app. When actively chatting. When PC has been freshly booted (at most an hour past boot). When PC has been on for some time and connected for some time. Latest occurance happened after a roughly 2 day 6 hour uptime for the mIRC client.
*) In most cases, can reconnect in about a minute w/o even closing mIRC.
*) Did NOT occur on system configuration previously (Win98SE, dialup connection)
* NOT connecting through firewall/proxy
System configuration:
Windows 2000 Professional
Pentium III 866MHz
640MB RAM
Plenty of free space on both HDs
Connection passes through Linksys Wireless Router to cablemodem
Router is forwarding Identd and DCC ports to PC using mIRC
mIRC 5.91 (Yeah, I keep meaning to upgrade...)
System is updated to most recent Win2K updates
Have not tested (yet):
*) Using IP instead of server name/DNS
*) Forwarding IRC connection ports specifically via router config.
Observations:
*) This is definitely a Win2K/WinXP issue. (No surprise - XP is built off 2K core techs, right?)
*) This appears, from what info I've seen, to be limited mostly to high speed Internet users. (Dialup reports seem to be more along the line of 'someone picked up the @#$@#$ phone again!')
*) This problem isn't limited to mIRC (judged by search of websites), but is pretty much a widespread issue with the most recent OS, and as such, we'll probably stuck dealing with this until Mi(c)ro$loth gets their act together.
My question: I'm looking for a more definitive solution... that is, if you did something to try to fix this and it was fixed... did it STAY fixed? It's pretty easy to uninstall software or change a setting, but it's kinda moot to do this if it's not going to have any effect. Guess I'm looking for a solution with longevity and not a false positive
Finally, in honor of this lovely error:
'Hundred Fifty Three
(Named in honor of Winsock Error 10053: Software caused connection abort)
I find I don't like hundred fifty three
It drives my brain right out of me
When typing, idle, or away from home
It stops mIRC with its deadly tome
It drops me when I read my mail
It drops me when I type like heyll
It drops me when I DCC
It drops me = AFK to pee
I do not like it on my box
I do not like this da## WinSock
I only want to stay online
I'll kill if slighted one more time
I don't like one hundred fifty three
It's pissing the @#$@# crap out of me!
- Apologies to Dr. Seuss
