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 exactly the same behavior on two independent machines.
Thanks for the info.
Merijn
On 7/12/2011 19:31, Francois PIETTE wrote:
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 which intercept socket communication
for malware. So here turn all security on, do an complete malware
check (update your software !). Also try to detect root kits which may
be there.
--
francois.pie...@overbyte.be
The author of the freeware multi-tier middleware MidWare
The author of the freeware Internet Component Suite (ICS)
http://www.overbyte.be
----- Original Message ----- From: "Merijn Bosma" <bo...@xs4all.nl>
To: <twsocket@elists.org>
Sent: Tuesday, July 12, 2011 1:49 PM
Subject: [twsocket] TWSocket.Close() blocks on certain machines
aftersending UDP
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.
The relevant code boils down to:
with TWSocket.Create(nil) do
begin
Proto := 'udp';
Port := some port;
Addr := some ip;
Connect();
SendStr('some data');
Close();
Free();
end;
Very simple, and works great.
Now on two machines we have an issue while using this code. The call
to Close() will block for 4 to 6 seconds if:
- I'm sending to an IP address within my own subnet
- There is no actual PC at that IP (doesn't have to be running a UDP
server, just a PC with that ip address).
I've tried with different NIC's, and now I have a NIC on USB, which
gives this problem on the 2 machines mentioned before (Win 7 Pro
SP1), but do not have the same issue on another machine (Win 7 Pro SP1).
Obviously there is something with these two machines, but I'd like to
know what is causing this to give me some control over it. These are
brand new machines, firewall is disabled and all pre installed
software is removed. I also have a support call at the manufacturer,
but since there is not much promising result from them I'm hoping
anyone here can give me a pointer in the right direction.
Thanks and regards!
Merijn
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
