This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
tcp_ip_patch [2010/04/26 02:56] – lucy | tcp_ip_patch [2015/08/15 04:21] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
===== TCP/IP patch ===== | ===== TCP/IP patch ===== | ||
- | Windows versions beginning with XP SP2 limits opening TCP connection attempts to 10 at any given moment. If there are more concurrent TCP connection attempts, Windows generates a warning: | + | Windows versions beginning with XP SP2 limits opening TCP connection attempts to 10 at any given moment. If there are more concurrent TCP connection attempts, Windows generates a warning:\\ |
- | + | [[http:// | |
- | [[http:// | + | Since XP SP2 there are only 10 concurrent TCP connection attempts possible. This does not limit the total number of connection attempts, just the amount that can be opened concurrently, |
- | + | Event 4226 warnings from normal use of BitComet does not indicate a problem, and is to be expected.\\ | |
- | Since XP SP2 there are only 10 concurrent TCP connection attempts possible. This does not limit the total number of connection attempts, just the amount that can be opened concurrently, | + | |
- | + | ||
- | Event 4226 warnings from normal use of BitComet does not indicate a problem, and is to be expected. | + | |
(A connection attempt is a query to a computer, if it accepts the TCP connection or not. If the target computer does not accept the connection, it will wait a few seconds, until a timeout occurs and the connection attempt will be canceled.) | (A connection attempt is a query to a computer, if it accepts the TCP connection or not. If the target computer does not accept the connection, it will wait a few seconds, until a timeout occurs and the connection attempt will be canceled.) | ||
- | BitComet 0.55 and above has been modified so that it can work within this limit without any configuration changes. | + | BitComet 0.55 and above has been modified so that it can work within this limit without any configuration changes.\\ |
- | + | With normal usage of BitComet, the target number of peers are obtained in less then a minute with or without the TCP limit in place, so it is only recommended that you install the patch **only if you know exactly what you are doing**, and have a specific reason for wanting to do so.\\ | |
- | With normal usage of BitComet, the target number of peers are obtained in less then a minute with or without the TCP limit in place, so it is only recommended that you install the patch **only if you know exactly what you are doing**, and have a specific reason for wanting to do so. | + | |
If you choose to apply that patch, you will be able to change the Max Simultaneous TCP connection attempts in the BitComet Options -> Advanced -> TCP/IP Limit. | If you choose to apply that patch, you will be able to change the Max Simultaneous TCP connection attempts in the BitComet Options -> Advanced -> TCP/IP Limit. | ||