Re: SIO_UDP_CONNRESET control code doesn't seem to be working

Yep..Thats one of my questions..
Even though the WSAInitiateRecv throws up this error, can I expect the
posting of buffers on to IOCP is successful? If so, the solution would be
simple just by ignoring it.

Thanks,
Jagadish

"Alexander Nickolov" wrote:

Why don't you simply ignore the error? It's not like anything
will change on the UDP layer because a send failed...

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: agnickolov@xxxxxxxx
MVP VC FAQ: http://vcfaq.mvps.org
=====================================

"Jagadish" <Jagadish@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:247065C6-0975-4CAE-BE84-AE17BC7E24F6@xxxxxxxxxxxxxxxx
Hi,

I have a server which uses UDP socket communication along with IO
completion
ports.

I ran into a problem of WSAECONNRESET (10054 error code) when trying
initiate a recv over a UDP socket. As per my investigation, this is due to
the ICMP port unreachable error that happenned on previous send.

So, As per the article,
http://support.microsoft.com/default.aspx/kb/263823, I applied the patch
to
disable SIO_UDP_CONNRESET before any data transfer happened on the socket
(I
did this after the bind. Not sure whether this really makes any
difference. I
hope it shouldn't). FYI, I used asyncronous WSAIOCtl call as I am using
IOCP. WSAIoctl calls are successful.

But still its been observed that WSAInitiateRecv is throwing up 10054
error.

Any clues on what might be wrong? Whether the patch mentioned in the
article
is applicable for sockets with IOCP as well?

Whether posting of buffers using WSAInitiateRecv will be successful even
after the 10054 error?

Any help is highly appreciated.

Thanks,
Jagadish



.