No buffer space available

[BjФrn Felten]

Since a few days back, I keep getting this error:

{W32 API error 10055} No buffer space available

It only concerns IPv4 nodes (all of them). The only way to send those
packages away is to start Windows in Safe Mode, and then it takes just a few
seconds for all of them -- sometimes up to four or five; the rest of the nodes
polling 2:203/0 use IPv6, fortunately.

Now, I know that the 10055 error usually has to do with too many ports open
or something like that, so I tried:

maxservers 2
maxclients 2

I never needed that before, but leave no stone unturned. But no difference
at all.

I would greatly appreciate any tips on how to fix this problem (I can't run
in Safe Mode all the time).

[Dan Clough]

-=> BjФrn Felten wrote to All <=-

BF> Since a few days back, I keep getting this error:

BF> {W32 API error 10055} No buffer space available

BF> It only concerns IPv4 nodes (all of them). The only way to
BF> send those packages away is to start Windows in Safe Mode, and
BF> then it takes just a few seconds for all of them -- sometimes up
BF> to four or five; the rest of the nodes polling 2:203/0 use IPv6,
BF> fortunately.

BF> Now, I know that the 10055 error usually has to do with too
BF> many ports open or something like that, so I tried:

BF> maxservers 2
BF> maxclients 2

BF> I never needed that before, but leave no stone unturned. But
BF> no difference at all.

BF> I would greatly appreciate any tips on how to fix this problem
BF> (I can't run in Safe Mode all the time).

Probably too many sockpuppets open.



... If at first you don't succeed, destroy all evidence that you tried.
=== MultiMail/Linux v0.52

[Michael Dukelsky]

Hello BjФrn,

Sunday April 21 2024, BjФrn Felten wrote to All:

BF> Since a few days back, I keep getting this error:

BF> {W32 API error 10055} No buffer space available

BF> It only concerns IPv4 nodes (all of them). The only way to send
BF> those packages away is to start Windows in Safe Mode, and then it
BF> takes just a few seconds for all of them -- sometimes up to four or
BF> five; the rest of the nodes polling 2:203/0 use IPv6, fortunately.

Did you try this?
https://learn.microsoft.com/en-us/troubleshoot/windows-client/networking/connect-tcp-greater-than-5000-error-wsaenobufs-10055
https://answers.microsoft.com/en-us/windows/forum/all/internet-connection-lost-socket-error-10055/07c03b68-56ae-4872-abed-2073e4d81bab

You may also check for malware. And run `netstat -b` to see the programs with
established connections.

Michael

... node (at) f1042 (dot) ru

[Bj÷rn Felten]

Michael Dukelsky -> Bj├╢rn Felten skrev 2024-04-21 21:36:

Thank you for the two links. Although I don't think I have ever found
anything useful on Microsoft's site, I have read the first article but missed
the second one.

1. Registry changing is always my last choice. For ports above 5000, I'd
rather port-forward the bink port to a number below 5000.

2. The second one was exciting since it involved cmd. I'll keep you posted
(if you like).

MD> You may also check for malware.

That's my first suspicion; however hard that is to believe, after a new
installation, the problem remained.

MD> And run `netstat -b` to see the programs with established connections.

<banging head on keyboard> BOC! How could I not think of that? Meh...

[Nick Andre]

On 21 Apr 24 14:08:12, Bj*Rn Felten said the following to All:

BF> {W32 API error 10055} No buffer space available

This problem happens here when BinkD runs for long periods of uptime.

After about a few months, the same error happens. 10055 creeps up on a few
connections and after a few days, escalates to all connections failing.

Whether this is a problem with the Windows stack or BinkD, a solution of sorts
is to kill BinkD, flush the network stack and relaunch via a nightly task.

taskkill /f /im binkd.exe
ipconfig /release
ipconfig /renew
arp -d *
nbtstat -R
nbtstat -RR
ipconfig /flushdns
ipconfig /registerdns
start /min binkd.exe xxxxxx.cfg

Has worked here for years.

Nick

[BjФrn Felten]

Nick Andre -> All skrev 2024-04-22 16:33:
NA> Has worked here for years.

Thanks. That was one exciting batch file. I really must try that. Nothing so
far has helped. All I've accomplished is I've lost IPv6... :(