I tried connecting to any MUD (I tried like 8) and they all get an error "No buffer space available". Someone wanna tell me what this means? I was connected to the internet, because I was talking to various people on AIM. And I have a cable connection.
Buffer error
Posted by Zeno on Mon 18 Aug 2003 06:56 AM — 4 posts, 12,075 views.
This message is error code WSAENOBUFS.
WSAENOBUFS should occur when the system has not enough memory or other system resources to open new TCP/IP socket or to handle socket data. It looks like that in most cases the problem occurs when total count of opened sockets reaches some magical number. MS writes that this limit is 3976 simultaneously opened sockets but it seems that on Win9x systems the real limit is much lower.
Because the TCP/IP system doesn't free sockets immediately when they are closed (socket remains allocated for 240 seconds after application closes it) it is possible that system will report WSAENOBUFS due to lack of free socket resources.
Do a Google search on "WSAENOBUFS". Here is one of the responses I found ...
http://www.experts-exchange.com/Programming/Programming_Platforms/Win_Prog/Q_10108972.html
WSAENOBUFS should occur when the system has not enough memory or other system resources to open new TCP/IP socket or to handle socket data. It looks like that in most cases the problem occurs when total count of opened sockets reaches some magical number. MS writes that this limit is 3976 simultaneously opened sockets but it seems that on Win9x systems the real limit is much lower.
Because the TCP/IP system doesn't free sockets immediately when they are closed (socket remains allocated for 240 seconds after application closes it) it is possible that system will report WSAENOBUFS due to lack of free socket resources.
Do a Google search on "WSAENOBUFS". Here is one of the responses I found ...
http://www.experts-exchange.com/Programming/Programming_Platforms/Win_Prog/Q_10108972.html
Yeah, when I got that error, my task manager wouldn't open and I couldn't open any webpages yet AIM was fine. That site looked helpful except for the fact it deals with how to fix it on NT and Win95. I have WinXP. I'll try searching for it.
Sounds like AIM had its socket, but Windows uses TCP/IP more and more these days, so the other things were trying to get one and failing. MUSHclient just told you about it, that's all. :)