 CopaMundialThe Artist Formerly Known AsPremium
join:2005-12-23
Happy 2008
1 edit | First, make sure that your "Max Half Open" Connections is lower than the number you set for Windows with the TCPSys patch.
I used that patch to bump it from 10 to 50, so I set my max half open in BitComet to 45. In your case I think you said you set it at 100, which seems higher than necessary to me, but if you leave it there make sure that your Max Half Open setting is lower than that.
That's a different number than the Max Connections per Torrent or Connections to keep per torrent... the "Half Open" connections refers specifically to NEW connections that are just being formed. So it can be a lower number than your "Max Connections Per Torrent" ... meaning BitComet can be forming 45 new connections, while holding 100 others.
I think what's happening in your case is that eventually BitComet is holding all of the Half-Open TCP connections, that means your browser or chat client is just SOL when it wants to start up.
You can check to see if this is the case by looking at your event viewer under the "system" tab... if you see TCP 4226 errors errors then that means you're maxing out your half open connections.
If you see those, then follow these steps:
1) Re-Run that TCPsys patch (some windows updates will make that value revert back to the original 10). When you re-run it I would advise setting it to a lower number (like 50). There's no way your PC ever needs 100 connections forming simultaneously... not even w/ P2P clients. (link for the patch if you don't have it anymore »www.lvllord.de/ )
2) Set that Max-Half Open connections in BitComet to a number lower than what you put the windows limit to with the TCPsys patch. |
