Home

A free C++ BitTorrent/HTTP/FTP Download Client

known_client_issues_and_incompatibilities
 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
known_client_issues_and_incompatibilities [2010/05/05 03:59] lucyknown_client_issues_and_incompatibilities [2015/11/17 04:48] (current) – [My file download stops at 9x.x%. What can I do about that?] the_unusual_suspect
Line 23: Line 23:
 This issue is not inflicted by BitComet, it is Nvidia's firewall that is causing the problem. This issue is not inflicted by BitComet, it is Nvidia's firewall that is causing the problem.
  
-Sources from http://forums.nvidia.com/lofiversion/index.php?t2682.html +//Sources from// http://forums.nvidia.com/lofiversion/index.php?t2682.html
  
 ---- ----
Line 57: Line 57:
 **Cause of this issue** **Cause of this issue**
  
-The limit was added to prevent computers from unknowingly being used in a type of Denial-of-Service attack known as a "Syn Flood", in which your computer sends an endless stream of connection requests (SYN's) to another computer. (A SYN that has not yet been followed up on is a half-open connection.) This barrage of SYNs fills up all of that computer's "slots" for incoming connections, so it cannot respond to anyone else until those slots are cleared. +The limit was added to prevent computers from unknowingly being used in a type of Denial-of-Service attack known as a "Syn Flood", in which your computer sends an endless stream of connection requests (SYN's) to another computer. (A SYN that has not yet been followed up on is a half-open connection.) This barrage of SYNs fills up all of that computer's "slots" for incoming connections, so it cannot respond to anyone else until those slots are cleared.\\ 
- +Your computer never follows up on any of these requests, it just keeps sending more SYNs. The attacked computer gradually times-out uncompleted requests and reopens its slots, but your computer just fills up those cleared slots with more SYNs. The result is that nobody else can find an open slot to connect to on that computer.\\ 
-Your computer never follows up on any of these requests, it just keeps sending more SYNs. The attacked computer gradually times-out uncompleted requests and reopens its slots, but your computer just fills up those cleared slots with more SYNs. The result is that nobody else can find an open slot to connect to on that computer. +Thus the denial-of-service.\\ 
- +By limiting the rate of half-open connections your computer can have pending (the number per second of SYN requests you can have that haven't been converted to fully-open), you give the attacked computer time to clear its slots before you can re-attack them. Other computers will have a chance to find an open slot and connect.\\
-Thus the denial-of-service. +
- +
-By limiting the rate of half-open connections your computer can have pending (the number per second of SYN requests you can have that haven't been converted to fully-open), you give the attacked computer time to clear its slots before you can re-attack them. Other computers will have a chance to find an open slot and connect. +
 No legitimate software application should ever behave this way for any reason, or need to start so many connections unless it's attacking another computer. Do not attack other computers. This usually happens when you've been zombied and taken over by malware, because you were careless about your firewall. No legitimate software application should ever behave this way for any reason, or need to start so many connections unless it's attacking another computer. Do not attack other computers. This usually happens when you've been zombied and taken over by malware, because you were careless about your firewall.
  
-This half-open limit won't affect the speed of your torrents. Connection attempts from you will open at a steady rate of about 10 per second, until your target of successful connections is reached (which, in almost all cases, will be less than one minute). Altering this setting should only be done by expert computer users, who have a specific reason for making this change. +This half-open limit won't affect the speed of your torrents. Connection attempts from you will open at a steady rate of about 10 per second, until your target of successful connections is reached (which, in almost all cases, will be less than one minute). Altering this setting should only be done by expert computer users, who have a specific reason for making this change.\\ 
- +The Pedantic Part: A connection attempt (half-open connection) is an attempt to connect to another computer. If the TCP connection is accepted and confirmed (it's a three-part process) (don't ask), it is no longer "half open", as it becomes a completed TCP connection. If there is no response or no response to the response (we said, don't ask), the connection will remain in the "half open" state, until a time-out occurs (usually a few seconds) and the connection attempt is dropped (disconnected). The slot on the receiver becomes ready to accept another request for connection.\\ 
-The Pedantic Part: A connection attempt (half-open connection) is an attempt to connect to another computer. If the TCP connection is accepted and confirmed (it's a three-part process) (don't ask), it is no longer "half open", as it becomes a completed TCP connection. If there is no response or no response to the response (we said, don't ask), the connection will remain in the "half open" state, until a time-out occurs (usually a few seconds) and the connection attempt is dropped (disconnected). The slot on the receiver becomes ready to accept another request for connection. +Event 4226 Report, when generated by normal use of BitComet, is NOT a problem and is an expected, normal occurrance.\\ 
- +<html><span style=color:Red>Warning:</span></html> Recent versions of BitComet include a patch which can alter your system's tcpip.sys file, to change this rate limit. We strongly recommend this only be attempted by computer professionals, and only if there is a specific reason for wanting to change said limit, as it could cause problems, or make the system become unstable. Use this at your own risk. Don't ask for help recovering from it, they'll only laugh at you. 
-Event 4226 Report, when generated by normal use of BitComet, is NOT a problem and is an expected, normal occurrance. +
- +
-**Warning:** Recent versions of BitComet include a patch which can alter your system's tcpip.sys file, to change this rate limit. We strongly recommend this only be attempted by computer professionals, and only if there is a specific reason for wanting to change said limit, as it could cause problems, or make the system become unstable. Use this at your own risk. Don't ask for help recovering from it, they'll only laugh at you. +
  
 ---- ----
Line 79: Line 72:
 ==== What are these “_padding_file…” things in the filelist? ==== ==== What are these “_padding_file…” things in the filelist? ====
  
-When downloading a BT task where not all of the files are selected, BitComet must create a file containing boundary data. This data will be saved at present time, in a special file: //taskname.piece_part.bc!// +When downloading a BT task where not all of the files are selected, BitComet must create a file containing boundary data. This data will be saved at present time, in a special file: //**taskname.piece_part.bc!**//\\
 BitTorrent clients exchange data which has been broken down into small pieces, not entire original files. Often, one or more of these pieces may span over two or more files, making it necessary to download parts of a file that was not selected to be downloaded. In order for the selected files to be fully downloaded and pass a hash check, this excess data must be present, and will be stored in this additional file. BitTorrent clients exchange data which has been broken down into small pieces, not entire original files. Often, one or more of these pieces may span over two or more files, making it necessary to download parts of a file that was not selected to be downloaded. In order for the selected files to be fully downloaded and pass a hash check, this excess data must be present, and will be stored in this additional file.
  
-BitComet versions prior to v. 1.02 do not use this type of boundary data file (taskname.piece_part.bc!) and could, in some cases, cause valid files to fail a hash-check, if the task properties have been altered, or the files are manually hash-checked. +BitComet versions prior to v. 1.02 do not use this type of boundary data file (taskname.piece_part.bc!) and could, in some cases, cause valid files to fail a hash-check, if the task properties have been altered, or the files are manually hash-checked.\\
 This file (//taskname.piece_part.bc!//) must be present as long as the task is active in BitComet (as well as if, in the future, you need to reseed the torrent). It's not required, in any way however, with regards to the usage of the files after downloading. This file (//taskname.piece_part.bc!//) must be present as long as the task is active in BitComet (as well as if, in the future, you need to reseed the torrent). It's not required, in any way however, with regards to the usage of the files after downloading.
  
Line 98: Line 89:
  
     * The torrent is out of date without complete BT seeds. Only if someone makes up for the lacking seed or provides a long-time seed, can you complete the download, in this situation. But for video files, 0.y% will not affect much the rest of the file, so you may still be able to play it.     * The torrent is out of date without complete BT seeds. Only if someone makes up for the lacking seed or provides a long-time seed, can you complete the download, in this situation. But for video files, 0.y% will not affect much the rest of the file, so you may still be able to play it.
-    * Along with the large files (e.g. video files), there are sometimes other small image or text files contained in the BT task. As there might be no seed or there could be less seeds for these small files (since others may have chosen not to download them), this may prevent your finishing the task. In this case, it's recommended that you do not download (deselect) these extra files.+    * Along with the large files (e.g. video files), there are sometimes other small image or text files contained in the BT task. As there might be no seed or there could be less seeds for these small files (since others may have chosen not to download them), this may prevent your finishing the task. Under normal circumstances you should always download all the files so you can fully seed the torrent for others, but In this case, it's recommended that you do not download (deselect) these extra files if they are not available in the swarm.
     * The torrent maker included by mistake a system file in the torrent (such as //thumbs.db// or //desktop.ini//), which in the meantime got updated by Windows. Thus the piece containing the file will fail the hash check constantly. Check for such files in your torrent task and deselect them.     * The torrent maker included by mistake a system file in the torrent (such as //thumbs.db// or //desktop.ini//), which in the meantime got updated by Windows. Thus the piece containing the file will fail the hash check constantly. Check for such files in your torrent task and deselect them.
     * You are getting rubbish (corrupted) data (pieces which fail the hash-check and are discarded). This can occur due to bad peers but sometimes this is also caused by some faulty implementations of NAT on some SOHO routers. Make sure you're not in the DMZ. A firmware update might help.     * You are getting rubbish (corrupted) data (pieces which fail the hash-check and are discarded). This can occur due to bad peers but sometimes this is also caused by some faulty implementations of NAT on some SOHO routers. Make sure you're not in the DMZ. A firmware update might help.
Line 118: Line 109:
  
 ---- ----
--[[configuration_and_user_settings|Previous Page]] -[[torrent_related|Next Page]] +-[[configuration_and_user_settings|Previous Page]] -[[torrent_related|Next Page]]\\
 -[[start|Main Index]] -[[start|Main Index]]
 
known_client_issues_and_incompatibilities.1273031943.txt.gz · Last modified: 2015/08/15 04:21 (external edit)
Recent changes RSS feed Driven by DokuWiki