Article on speeding up uTorrent

Anything that doesn't fit in the other forums goes here. Well, really not anything - but you get the idea


Article on speeding up uTorrent

by Guest on Fri Jun 23, 2006 2:53 pmPostQuick Link PostView Single Post

I thought this articlewas excellent. It could be improved in one element: What are the good/best ports for uTorrent?

FYI...
Some Torrent sites, eg BTmusic blacklist some ports:

QUOTE:
Why do I get a "Rejected by tracker - Port xxxx is blacklisted" error?
Your client is reporting to the tracker that it uses one of forbidden ports.
Pedro's BTMusic Tracker does not allow clients to use ports within 0 - 49151 range.
The allowed ports list includes the following port ranges:
Allowed ports 49152 - 65535
In order to use our tracker you must configure your client to use any port range within the region 49152 through 65535 (details can be found here: IANA). Notice that some clients, like Azureus 2.0.7.0 or higher, use a single port for all torrents, while most others use one port per open torrent. The size of the range you choose should take this into account (typically less than 10 ports wide. There is no benefit whatsoever in choosing a wide range, and there are possible security implications).

These ports are used for connections between peers, not client to tracker. Therefore this change will not interfere with your ability to use other trackers (in fact it should increase your speed with torrents from any tracker, not just ours). Your client will also still be able to connect to peers that are using the standard ports. If your client does not allow custom ports to be used, you will have to switch to one that does.

Finally, remember to forward the chosen ports in your router and/or open them in your firewall, should you have them. See the Why am I listed as not connectable? section and links therein for more information on this.

:lol:
Guest
 

by Ganesh on Sat Jun 24, 2006 12:18 amPostQuick Link PostView Single Post

Thanks for showing your appreciation.

With regards to the blocked ports, these are tracker specific - some trackers are fussy over ports, some are not.

If a user gets the message, then he/she has to change his port settings to meet the tracker requirement.

Some trackers may overlap, eg port 48955 may be blocked on one, but allowed on another. This is why it is not highlighted in the article.
Ganesh
Administrator
 
Posts: 488
Joined: Tue Jun 25, 2002 10:20 am
Location: Singapore




Return to General Chat



Who is online

Users browsing this forum: No registered users and 1 guest

cron