Geek asks and answers

Multicast socket.close takes 3 minutes with TTL> 1

On some Windows machines, I see that calling multicast socket.close takes ~ 3 minutes.

This is reproducible in both Java and .NET for various types of network adapters and Windows.

It does not play on most machines, but those in which it seems to follow the same pattern. TTL> 1 causes a 3 minute socket. Close and any TTL == 1 seem to close the socket almost instantly.

My questions is - does anyone else see this problem, and does anyone know why this is happening?

+3
source share
2 answers

, Socket.Close() 3 , , TTL > 1: , RAS (RRAS). KB : http://support.microsoft.com/kb/2555948/en-us

netsh interface ipv4 set global multicastforwarding=disabled Socket.Close() .

+2

, . ++ Windows 7 UDP. , , , .

+1

More articles:


All Articles