Geeks With Blogs

News

qrcode

Lance Robinson

Create Your Badge

Lance Robinson is a software engineer in Durham, Chapel Hill, Raleigh, and surrounding areas. More about Lance.

 Subscribe


Lance's TextBox » About Me » My Resume »Twitter
Last month I mentioned winsock error 10053, "Software caused connection abort" (basically, the error means that something on the localhost caused the connection to be closed), and how it is so often caused by virus scanners. I pointed out that this is not always the case, and sometimes the problem is very difficult to troubleshoot. But don't worry, this is pretty common and it is most likely not a bug in your code, just something that needs to be considered when implementing error handling.

Besides AV software, another common cause of this error is that a remotehost stops acknowledging receipt of TCP packets. When TCP packets are sent to a remotehost, and the remotehost does not acknowledge that packet, the local socket will attempt retries - but if the remote host never responds, a 10053 error will occur. Posted on Wednesday, July 20, 2005 7:52 AM Programming | Back to top



Comments on this post: Winsock error 10053: Part 2

# re: Winsock error 10053: Part II
Requesting Gravatar...
you saved me a lot of trouble my av was the problem thanks
Left by Ross on Aug 17, 2005 8:06 AM

# re: Winsock error 10053: Part 2
Requesting Gravatar...
me 2 , mcafee access protection . ;-))
Left by Chris on Aug 08, 2006 12:51 PM

# re: Winsock error 10053: Part 2
Requesting Gravatar...
I have DHCP server. In last week i saw the error 10053 (2745) in windows 2003.

From that day i facing the problem of connectivity. After every 20-30 minutes client machines are automatically drop the connectivity from server and again some time automatically detect connectivity.
Left by Sandeep Acharekar on Feb 10, 2007 3:45 AM

# re: Winsock error 10053: Part 2
Requesting Gravatar...
host based smtp server are known to cause this error
An ISP is usually rejecting requests from such type of smtp servers
Left by knewt on Mar 14, 2007 3:56 AM

# re: Winsock error 10053: Part 2
Requesting Gravatar...
We had this error occur at a 10 minute intervals after establishing a TCP/IP connection to a host system. This was finally traced back to a bad ROUTE entry on the Server. The ROUTE entry used the Server's network card's address, instead of the Gateway device's IP address. This caused the Gateway to not know how to route a packet sent from the Server after the ARP timeout period.
Hope this helps someone else.
Left by Don Miller on Jun 08, 2007 3:15 PM

# re: Winsock error 10053: Part 2
Requesting Gravatar...
I am useing an SMTP through an msn server. As Qwest DSL does not support SMTPs, and I am getting the error 10053, everything was working great up tuill a few days ago, now nothing works.
I have been using smtp.email.msn.com as the outgoing smtp. Is my ISP blocking these transmitions now? Or is it the MSN e-mail I am using to piggyback on?
Left by Paul on Jun 28, 2007 4:53 PM

# re: Winsock error 10053: Part 2
Requesting Gravatar...
My laptop was running ok until I uninstalled some softwares ( fix-it utility 7, and ...) and stopped some software from starting up. Then I got disconnection problems for windows live messenger, yahoo messenger and skype. All these software will drop connection in about every 13 minutes. I identified it as an error 10053 by looking the windows live messenger's connection log file. For every 13 minutes "Zone_Net CTCPNetworkLayer::OnMessage (013B12D8) (2) >> Got WM_WSASELECT_MESSAGE(1055) from WSAAsyncSelect for socket = 2088, error = 10053, event = FD_CLOSE" appears in the log file. I tried everything I can think of (uninstalled firewall; reinstall fix-it utility and restore to a old checkpoint; then uninstalled avg antivirus and fix-it utility) none of them worked. I am so frustrated.
Left by Laser on Oct 27, 2007 12:56 AM

# re: Winsock error 10053: Part 2
Requesting Gravatar...
I have a question can a virus cause this too? I accidently went on a site that you can't get out of it freezes your computer and shows everything on your desktop screen and makes everything go weird then my computer crashed and when I went back I had this error on IE, FX, and safari.
Left by D on May 12, 2008 8:02 PM

# re: Winsock error 10053: Part 2
Requesting Gravatar...
Thanks Don Miller, your advice helped me out. Your mention of the ARP timeout is what clued me in, as I was getting this error every 10 minutes.

I have a router behind a router. The internal router was in the DMZ of the external one. I'm pretty sure the trouble came because both routers essentially had the same external IP address & the keep-alive packet that was sent after the 10 minute ARP timeout period, did not know which one to send it to.

I simply logged into the external router & removed the internal router from DMZ mode, and then just forwarded all the ports I needed to it instead.

It's more of a maintenance headache... but at least it works.
Left by Eric on May 31, 2008 6:00 PM

# re: Winsock error 10053: Part 2
Requesting Gravatar...
I got 10054 error in windows 2003. The client can connect to server, but it will fail to send any data.
Left by imfirewall on Jun 09, 2008 11:17 PM

# socket error: 10053 (2745)
Requesting Gravatar...
please help me to solve this error problem
Left by shraaa on Aug 24, 2009 6:12 PM

# re: Winsock error 10053: Part 2
Requesting Gravatar...
Laser, you sound just like me. I have concluded?that my router is not responsible but I could be wrong.
I say this because I have tried to connect to the web using a phone as a modem, switched connections from ISP to another, firewall off, Antivirus off, and still the problem of 'error 10053' is not solved.
Left by Greaterman on Oct 18, 2009 3:26 AM

# re: Winsock error 10053: Part 2
Requesting Gravatar...
By the way, my mail client Thunderbird works ok, gtalk works fine including the video call.. but msn messenger is not working though.
Left by Greaterman on Oct 18, 2009 3:32 AM

# re: Winsock error 10053: Part 2
Requesting Gravatar...
Hi all - i seem to have the same problem when i print out big jobs to a LFP - it will print fine the whole time, and then suddenly just stop printing - and gives a winsock error 10053.

any suggestions what we can do to fix this issue?
Left by willem on Mar 16, 2010 8:06 AM

Your comment:
 (will show your gravatar)


Copyright © Lance Robinson | Powered by: GeeksWithBlogs.net