After choosing a suitable client read the FAQ on the client
homepage for any configuration tips, install (restarting your browser
may be required), find files you are interested in, click the link and
start downloading.
There are two trackers UDP and HTTP; the UDP tracker is better
optimized and puts less strain on the server, however it is not
supported by all clients, and the HTTP tracker is supported by all
clients, is more reliable for ratio updates, but more of a strain on
the server. Neither tracker has any affect on transfer speeds.
There are actually a few factors which may contribute to this
problem. Though 99.9% is the most common, it actually happens with
percentages in the high 90s (96%, 97%, 98% and anything in between).
There may be an anti-leech protection in effect limiting transfers
to you. Many clients does have this feature to ensure peers give back
what they have taken to the swarm.
The final piece(s) may be something changeable. Check to see what is
left on the download. If the file(s) in question are ". DS_Store," "
Thumbs.db," or "desktop.ini," you may select these files and choose to
omit them from the download. If the seeder's version of these files
changed, then they will fail the hash check, preventing anyone from
getting the original. Similarly, if on your side, these [hidden] files
are "read only" and/or protected, your client will keep downloading
and discarding that which cannot be replaced.
There may be a physical problem preventing you from completing the
download. Try stopping the torrent, run scandisk, and restarting the
torrent. This will fix any errors on your harddrive.
The more pieces you have, the harder it becomes to find people who
have the pieces you need. That's why downloads sometimes slow down or
even stop completely. Just be patient and you will get the remaining
pieces.
There was no response to a request sent to a peer or tracker
normally a result of the tracker/server being to busy to process your
request at that time, just leave it open.
This could be a symptom for a range of problems resulting in you
not being able to connect to the tracker, you internet connection
going down, firewall/router interfering with your connection,
server/tracker being busy or even being banned from a tracker, most
commonly this error will resolve itself or you could try restarting
your client.
Normally the result of a blocklist application ( PeerGuardian/Protowall/SafePeer)
or firewall with specific IP blocking function, in the case of a
blocklist application try updating the blocklist or in the case of a
firewall verify your exemption settings.
This error is is caused by Internet Explorer failing to save the
.torrent file correctly in its temporary directory when the download
link is left clicked, try right clicking on the link and choose "Save
As" directing the path to a directory specifically for .torrent files
or just use a different browser.
Unless configured no to do so Bit Torrent client allocate the space
required to store files on the hard drive when the torrent is started,
this error occurs when there is insufficient space or when the hard
drive is in FAT32 format and the file exceeds the 4GB limit in this
case convert your hard drive to NTFS.
XP compresses the temporary internet files after a certain point
which causes this error, either clear your temp files or save the
.torrent directly to you hard drive and launch it from there.
Sometime bittorrent still runs in the background, and if you start
more than one gui (the same torrent) it will give you permission
denied, go to Task manager and close down all bt-gui processes.
You client doesn't support the UDP protocol, some torrents are
multitracker torrents which may include a UDP tracker announce.
Why am I getting "Problem Connecting to tracker - [ errno http error
]403 'Forbidden (client banned)" error?
The tracker for the torrent has banned the client that you are using
try a different one.
Unless configured otherwise some clients will keep all the files in
a torrent open during the downloading process. This error occurs with
some of the larger multi-file torrents, which can have hundreds or
thousands of component files. When the number exceeds the OS limit,
the OS refuses to allow them all to be opened, preventing the client
from accessing them. To resolve the problem either limit the number of
files the client will have open at any one time or increase the OS
limit for the number of open files.
The main reasons for this are:
1. The torrent may have been out-of-sync with the site rules.
2. The torrent was not seeded. Torrents expire after 5 days without a
seed.
3. It was a bad release. A replacement will probably be uploaded to
take its place.
4. The torrent expired. Older torrents are sometimes automatically
deleted when the peer count gets high to avoid running out of RAM and
killing the server.
Most think just seeds are enough for a quick download, but leechers
also affect transfer speeds. You may download the pieces they have
already acquired. However, if there are too many leechers, they may
already be taking all the speed.
If you are behind a firewall, then this will limit the number of
peers you are able to connect to. Although you can make outgoing
connections to peers, they cannot make any connections to you. Forward
the ports your client is using and you noticed you'll get more
connections.
Although uploading is a good thing, if you are maxing out your
upload stream, you will saturate your bandwith, thus lowering your
download speed, as well as slowing down any other internet action(s).
How TCP/IP works, is when you download a packet, you must reply to the
sender saying you received it. This will prompt the sender to send
another packet. If you are at max on uploads, it may take a while for
your reply to get to it's destination, which prevents you from getting
the next packet. The best way to battle this, is to limit your uploads
to 80% of your maximum speed. IE: If you have a maximum upload rate of
40 kilobytes per second, limit that to 32 kilobytes per second. The 8
kilobytes is enough buffer for replies and even browsing the web.
Remember, bittorrent is a sharing protocol. If you're being stingy
with the uploads, other clients won't transfer to you. Many clients
even tell you that your download rate is proportional to your upload
rate. This does seem to be the case in small to medium swarms, but
sometimes doesn't apply to large swarms. In any case, be sure to
upload as much as you can.
Whatever the problem may be, be sure to give it some time. Sometimes
it just takes time to connect to the right peers. Bittorrent is the
best sharing protocol out there and is designed to more often than
not, max out your download speed.
The majority of NAT errors are a result of incorrectly configured
firewalls or routers, open the listening port that your client is
using in your firewall and/or router, if your client uses a port range
try to limit this to around 10 ports any more is unnecessary and could
pose a security risk. If you don't know how to open ports check any
documentation that you may have or the "makers" support/help forum.
Portforward.com is very informative on this subject and remember
Google is your friend.
Some ISP's throttle the connection on the known default Bit Torrent
ports 6881 - 6889 so changing the listening port of your client will
help avoid the affects of this traffic restriction, some care should
be taken when selecting a port see Here for known port nasties.
The torrent rating goes from 1 to 10, 1 being the worst rating, and
10 the best. When a torrent has not been rated yet, it will have a
"n/a" instead of the score. Please remember this is a rating system on
the quality of the torrent content, not how much you liked it or
disliked it.
