Damned Event ID 4226!
I’ve been doing alot of BitTorrent downloads with Azureus recently, that’s if it’s counted by the gigs instead of the number of files. I’ve done 18GB of downloads in 16 days as shown in the statistic console. Wow, that sounds like alot to me!
So at one time or others, my seeders were low. And at some points some torrents would go into Queued mode. At night I can’t surf any websites but my internet connection was active. Funny things happened and I didn’t think of it much. Until I found Event ID 4226 appeared in my system event log, and I wonder if those incidents had anything to do with this implementation.
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.
Yup, I’ve reached the so-called 10 half-open concurrent TCP connections limit, somehow or another. And so further connections are queued till the first 10 has done its job. I haven’t actually gotten the whole limiting idea implemented by Microsoft in Windows XP SP 2, I just felt I don’t like being restricted. But if you want to know more, start from Microsoft Windows XP SP2 changelog page.
At any rate, I had went ahead and found a patcher (thanks to GRC newsgroup’s recommendation) and increased the irritating limit of 10 to 100. That’s 10-fold, my friend. I’ve tried more, but the patcher discouraged me as the original intention of Microsoft for such limits is to slow down spreading of worms. So I’ll stay at 100 and see what happens.
If you’re on Windows XP SP 2 and think that you’re affected by such limits (note that NOT everyone would be affected and I can’t exactly tell you how you would even need it), go ahead and use the patcher. Although I have no problems with it, neither the author or me would guarantee that it would be a smooth sail for you!