A couple of things that might help with people's confusion...
Port-forwarding is almost
essential if you're accessing the internet through a router, &
http://www.portforward.com has idiot-proof guides for most of the models available.
Next, the majority of ISP's list their options in terms of kilo
bits per second, whereas torrent-clients tend to work in kilo
Bytes per second - as stated in an earlier post, to find your upload-bandwidth in kilo
Bytes you need to divide your ISP's figure by 8, then calculate your 'maximum upload rate' as a percentage of that.
As an example of this, my broadband-package is
supposed to be 2Meg down, 256K up. The
true figures are 2272 kbps down, 288 kbps up - those are the statistics displayed if i open a web-browser & type
192.168.1.1 into the location-bar & press enter (that's the network-address of my router - see if you can access your's in the same way). Those bandwidth-figures equate to 284 KB down & 36 KB up, so i limit my upload-rate to 28 KB/s (just under 80%) in order to have a usable internet connection while i'm downloading.
(As a Linux-user, i intend to change to the
QoS network-queueing system, just as soon as i figure out the nuts & bolts involved - no idea if Windows can do the same thing, sorry
)
It's also important to note that using an
unlimited client can actually
slow things down, because of the way the TCP-protocol works - every packet of data has to send back an 'acknowledgement-of-receipt' to the sender, & if your bandwidth is flooded, these can fail to get sent properly, causing the same data to be sent more times than necessary.
I hope the link & the brief theory-lesson are helpful to someone - when i get that
QoS business sorted out, i'll probably come & gloat about it...