I'm pretty sure now [27/8/2012 19:00] that it is my router causing this problem.

I have a socket program that spawns 256 threads to query 256 IP's port 80. It
waits for them all to finish and then cycles round to begin another 256 threads.
I had to modify TCPIP.SYS to remove the tcpip.sys socket creation limit:for it
to function properly. viz: http://www.speedguide.net/read_articles.php?id=1497
At a 'random' point during the processing XP stops processing incoming requests.
In IE and chrome an attempt to connect to google will time out. Wireshark shows
DNS functions OK when i use chrome and attempt to connect to google. If i kill
the program after approx 1 hour XP starts accepting incoming packets. When it
starts workng again i still have the same LAN / WAN IP's. Following is proram
output after cancelling it.

C:\Cpp\Port80_Multithread\Debug>Port80.exe

End Time 20:37:44.109 25/8/2012
Start Time 20:10:10.218 25/8/2012 212.182.082.255

C:\Cpp\Port80_Multithread\Debug>-

Finally an hour later XP started processing TCP packets again
and chrome was able to show googles page without timing out.
I can't see any clues in pfirewall.log not that I expected to.
Can anyone shed some light on his behaviour please?

Even rebooting [restart] does not affect it. Now I'm wondering if it's the router!

Last edited by turnbui; August 27th, 2012 at 01:00 PM.
Reason: Even rebooting [restart] does not affect it. Now I'm wondering if it's the router!