Re: winsock error WSAENOBUFS(10055) from bind()
- From: "Volodymyr M. Shcherbyna" <v_scherbina@xxxxxxxxxxxxxxx>
- Date: Thu, 24 Apr 2008 15:48:06 +0200
This topic arises third time for last 2 monthes. Read this thread,
http://groups.google.com/group/microsoft.public.win32.programmer.networks/browse_thread/thread/820d7ff1938a424a/29e16b31ea79d44c?lnk=gst&q=Socket+server+connection+test#29e16b31ea79d44c
--
V.
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Ionel Maries" <ionel.mc@xxxxxxxxx> wrote in message
news:731d7150-7281-4cd3-b008-6cbca4c83d2f@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I'm trying to open a large number of connections using ConnectEx, but
i need to bind them first.
On windows xp after about 300 bind starts failing with WSAENOBUFS.
What should it do?
Is there some way that i could be notified when resources are freed
(via iocp preferably) ?
.
- Follow-Ups:
- Re: winsock error WSAENOBUFS(10055) from bind()
- From: Peter
- Re: winsock error WSAENOBUFS(10055) from bind()
- References:
- winsock error WSAENOBUFS(10055) from bind()
- From: Ionel Maries
- winsock error WSAENOBUFS(10055) from bind()
- Prev by Date: Re: TCP checksum failure with offloading disabled (0xFFFF)
- Next by Date: Re: localhost faster ?
- Previous by thread: winsock error WSAENOBUFS(10055) from bind()
- Next by thread: Re: winsock error WSAENOBUFS(10055) from bind()
- Index(es):
Relevant Pages
|
Loading
