Subject Re: [ib-support] Unusual server lockup 10061
Author Ann W. Harrison
At 07:33 PM 12/21/2001 +0000, Jason Chapman wrote:

>Everything is fine and then kerboom. I think the key is the INET10055 error
>(Buffer out of space), but I can't see what is causing it other than lots of
>small Blobs being retrieved by clients.

Have you looked for WSAECONNREFUSED and WSAENOBUF in Google or at the
MSDN site. MSDN didn't yield up any treasures for me, but Google
found these two.

0914 ยป WSAENOBUFS (10055) error.

If you take out your Captain Video Secret Decoder Ring, it becomes
clear that this means:

An operation on a socket could not be performed because the system
lacked sufficient buffer space or because a queue was full.

Not much better.

If you are trying to use an ephemeral (short-lived) TCP port above
5000, this may explain the message. By default, Windows NT 4.0 only
supports 5000 ephemeral TCP ports.

You can increase this by navigating to


Add Value name MaxUserPort, a type REG_DWORD, and set it to some decimal
number in the range of 5000 - 65534.

Once a port is closed, it takes 4 minutes (240 seconds) before the system
will reuse it. You can alter this behavior if you

Add Value name TcpTimedWaitDelay as a type REG_DWORD and set it to some
decimal number in the range of 30 - 300 seconds.


Receive the error "Socket RECV error 10055" on
connection attempts.


This is a problem with the stack buffer size and some
TCP/IP stacks. To resolve this problem simply add the
following line to your HOSTEX.INI file in the

[System.Settings] section : Max Winsock Receive Size = 4096


We have answers.