James, The full description of a 10053 error:

---
WSAECONNABORTED (10053) Software caused connection abort.

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).
---

The first thing I'd try is rebooting the machine to clear the TCP stack
(windows sometimes gets things stuck in the stack). Are there any
local sites you can try connecting too rather than across the Atlantic?
Do they perform any better at those hours? If they don't a call to
your ISP may be in order to ask if they are doing maintenance or
something of the sort at that time.

--
Carl MacDonald (aka Scotsman)
MadWolf Software

On Apr 27, 2007, at 1:49 PM, james wrote:

> Winsock Error: 10053