Socket error 10052 on UDP socket



We have a .NET 2.0 desktop application which sends and receives network packets over UDP.

Several users have reported an occasional socket error 10052 which happens when the code calls socket.BeginReceiveFrom on a the UDP socket.

What does this mean?

The official MS documentation for socket error 10052 says - quote:
"WSAENETRESET (10052) Network dropped connection on reset . The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. It can also be returned by setsockopt if an attempt is made to set SO_KEEPALIVE on a connection that has already failed."

This just doesn't make much sense for a UDP socket since UDP is a connectionless protocol.

I know that another close error code 10054 in connection with UDP sockets means that an ICMP message "Port Unreachable" was received, and I am wondering if 10052 might map to another ICMP message?

I have googled this for months, read network books, etc. but can't find anything.
Please help - what does socket error 10052 on a UDP socket mean?

Thanks in advance,
Jesper

.



Relevant Pages

  • Re: Multiple closed networks and UDP. Please help me.
    ... Each of the three computers will be in its own closed network. ... I have worked with TCP many times, but never UDP. ... When I open a socket to receive one UDP socket stream do I ... I believe that the TCP connection will be assigned based on the IP address. ...
    (microsoft.public.vc.mfc)
  • Re: Internet connection through PC
    ... You can craft your code to force your UDP traffic through a connection other ... You need to bind your socket to the IP of your GPRS adapter. ... > while keeping the eVC4 debug capability alive. ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: How to uniquely identify a UDP session at Winsock layer?
    ... For UDP, once a send is done, the socket will be auto-bound if it has not ... > Theoretically, I guess, a connection or session in uniquely identified ... > by "Source IP, Source port, Destination IP, Destination port". ...
    (microsoft.public.pocketpc.developer.networking)
  • Re: checking connection to server:port [socket]
    ... I need to check connection to server ... i think you just want to check a udp connection to a udp server. ... not a UDP socket connect. ...
    (comp.lang.ruby)
  • Re: SetSockOpt with SO_REUSEADDR parameter
    ... So I create multiple UDP sockets with the same port to send data. ... happening is that you are throwing away the old socket and replacing it with the new ... When the second client is connecting to server, I still get the error code ...
    (microsoft.public.vc.mfc)

Quantcast