D
duraisridhar
Hi All,
My active connection created by my application from windows 2000 to
Windows 2003 (or any linux machine) get closed as it receives
WSAENOBUFS error . While I googled , I come to know that this may occur
for the below reasons,
1) If Total Number of protocol exceeds 50 - this is not my case , as
my windows 2000 has protocols less than 10 .
2) When application tries to connect the port number greater than
5000 - Again this is not my case , since my application's active
connection which had transmitted some data
over the connection and get closed in middle with error WSAENOBUFS.
Can anybody point out what made my socket invalid with error
WSAENOBUFS. Is there any way I can overcome without affecting my
network transfer performance ?.
Thanks for your time.
Regards,
Sridhar D
My active connection created by my application from windows 2000 to
Windows 2003 (or any linux machine) get closed as it receives
WSAENOBUFS error . While I googled , I come to know that this may occur
for the below reasons,
1) If Total Number of protocol exceeds 50 - this is not my case , as
my windows 2000 has protocols less than 10 .
2) When application tries to connect the port number greater than
5000 - Again this is not my case , since my application's active
connection which had transmitted some data
over the connection and get closed in middle with error WSAENOBUFS.
Can anybody point out what made my socket invalid with error
WSAENOBUFS. Is there any way I can overcome without affecting my
network transfer performance ?.
Thanks for your time.
Regards,
Sridhar D