Re: [twsocket] TWSocket.Close() blocks on certain machines aftersending UDP

2011-07-12 Thread Arno Garrels
Merijn Bosma wrote: > Was Francois able to find a way to make sure this is the case, or a > work around? AFAIR the workaround was to do your own ARP request first in order to check whether the destination exists or not, utilizing the IP Helper API. -- Arno Garrels -- To unsubscribe or change

Re: [twsocket] TWSocket.Close() blocks on certain machines aftersending UDP

2011-07-12 Thread Merijn Bosma
On 7/12/2011 19:26, Arno Garrels wrote: That sounds very similar to an issue Francois reported several months back and which turned out to be a winsock bug IMO. In Vista+ winsock repeated the ARP request within a few seconds 2 times to get the MAC address that accepts packets for the destination

Re: [twsocket] TWSocket.Close() blocks on certain machines aftersending UDP

2011-07-12 Thread Merijn Bosma
New message while I was typing the reply to the previous one :) Fraincois, I've been able to reproduce this on a fresh installed machine (no internet connection). Windows firewall is disabled, no extra software installed. I think that will rule out a external software issue? Besides, we see ex

Re: [twsocket] TWSocket.Close() blocks on certain machines aftersending UDP

2011-07-12 Thread Francois PIETTE
I suggest you look at "security software" which may be installed on those PC. Some of those software (anti-malware, firewall, proxy,...) are malfunctionning in their interception of socket communication. So first do a test with every security software disabled. It may also be a virus or trojan

Re: [twsocket] TWSocket.Close() blocks on certain machines aftersending UDP

2011-07-12 Thread Arno Garrels
Merijn Bosma wrote: > Hi all, > > I've been using ICS for a long time, in different environments and on > different machines without problems. > Now I've stumbled upon a problem of which at the moment I don't know > how to find a solution for. It's regarding a snippet which sens data > using UDP.