Possible reason for download speed problems?

[Guest]

I like what I see so far :mrgreen:, but the speeds... :!: also if it's possible to have it so that it is easy to copy and paste the hash to make it easier for testing (better to ask this in the feature request forum huh). I ask that other users to test out their connections using DumpTorrent http://dehacked.2y.net/BT/DumpTorrentCGI.php and natcheck http://btfaq.com/natcheck.pl .

After running natcheck

Fail!

The connection was successful but a timeout occured reading or writing the BitTorrent client data.

My connection is valid (works with azureus and port configured correctly etc...) and utorrent reports network OK, but I do not understand why I have a timeout error. Oh yeah I did put the Bandwidth Allocation on High (anyway to have that to be default?).

Thanks!

[segosa]

Bandwidth allocation is relative to other torrents I believe, so having them all on High has the same effect as having them all on Normal. Think of it as priority.

[Guest]

I still get the same error

Attempting connect to: IP# port #

Fail!

The connection was successful but a timeout occured reading or writing the BitTorrent client data.

This is on the latest 1.1.2.

[Guest]

I have this problem too, most of the trackers show me as "passive".

[YeCkeL]

This is what is known as user errror:) Almost unfixable sometimes hehe.

toMpEr sounds like you did not either turn on Upnp in your router and active that port needed at router level *my linksys makes me* or you didnt forward the port properly your self as well try not to use black listed ports.

The blocked ports list include, but is not neccessarily limited to, the following:

Direct Connect

411 - 413

Kazaa

1214

eDonkey

4662

Gnutella

6346 - 6347

BitTorrent

6881 - 6889

In order to use use our tracker you must configure your client to use any port range that does not contain those ports (a range within the region 49152 through 65535 is preferable, cf. 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.

i use 56881 lol

[Guest]

It's been also recommended to change your Connection

> Incoming TCP listen port to something in the 48620-49150 range

(or any other unassigned port you can find at

http://www.iana.org/assignments/port-numbers

If you have a router, you may have to forward your ports.

http://www.portforward.com/ will tell you how.

port no. 49141 is a good port

[Guest]

Ran natcheck using 1.1.3 and it says it PASSES!!!

Hopefully this should solve the weird speed problems I had earlier.

Thanks!

[Guest]

running smooth as usual

tried a torrent with much more seeds than leechs.. took about 5sec to reach max (~1100kb/s)

[Guest]

works like a charm ("PASS!" )

using port 6970 btw. how evil of me, to stay so low.

(dont listen to everything you read.. )

[UTorrentUser]

Passed using 6112 with UTorrent 1.1.3

It is interesting. It says I passed on a VERY popular torrent rite now yet the speeds are ABYSMIL!!! Just, fucking, horrendous. It makes jesus cry to see a 4mb down/ 256kb up like unused.

Interesting indeed