Aug 19, 2011

Windows XP TCP/IP No buffer space available


I have isolated a problem down to this:

On Windows XP Pro, SP2 if one does an experiment where one tries to open TCP/IP sockets in a loop (bascially, listen port 7000, listen port 7001, etc.)

After approx 649 open sockets, one will start getting errors: No buffer space available (maximum connections reached?)

The question is, what registry settings etc. does one edit to increase the number of listening sockets one can open before receiving this error?


Take a look to this page:

Related posts:

  1. Why is crond listening on port 6550/tcp (fg-sysupdate)?
  2. Failed PCI Compliance – Port: 21 Protocol: tcp | Summary : attempts some buffer overflows
  3. Apache config: “no listening sockets available”
  4. Which is the default TCP connect timeout in Windows?
  5. How to get sockets which are listening on a specific port in linux?

Leave a comment