Switeck

That router is *INCAPABLE* of 300 megabit/sec via Wireless-N (WiFi) for your computer, period. You will be extremely lucky to reach 100 megabit/sec via Wireless-N (WiFi). Your internet speed tests show much lower numbers than your router is capable of, not even reaching 7 megabit/sec down or 3 megabit/sec up. Use the 2.5 megabit/sec upload settings from my chart.

Knowing why a troubleshooting guide doesn't work...would help a lot of others.

DreadWingKnight said, "The problem is the delusion of the private tracker admins that uTP gives any exclusivity advantage. They have more to worry about from seedboxes." One could also make the same claim that BitTorrent clients that use IPv6 are "unfairly favoring" other IPv6 BT clients. It's a nonsense claim, unless those clients are using EXCLUSIVELY IPv6...but uTorrent doesn't use just uTP or IPv6 by default.

Go to speedtest.net and run their tests while NOT running uTorrent or other heavy bandwidth-using apps.

Try disabling net.calc_overhead

3/4 of the advanced settings and even much of the speed settings can "cause trouble" if set wrong for your line/network. If I recall correctly, upgrading uTorrent v1.8.x to v2.x automatically changed bt.trans_disposition even if you manually changed that setting before. So why not Disk Cache settings? Disabling "reduce memory usage" (2nd checkbox) would seem a smart choice as well, if windows caching is disabled. uTorrent should still limit its disk cache to 32 MB.

Spyde, if your networking software and/or hardware cannot handle UDP packets very well, uTorrent v2.0 and up *WILL NOT RUN WELL* on your computer! But I don't see how that's in-and-of-itself uTorrent's fault. The UDP using stuff (DHT, Resolve IPs, Teredo/IPv6, and uTP) can all be disabled.

1st link in my signature, last post, very last part of that tells how to get Process Explorer to show uTorrent.exe's DLL list. Since svchost.exe is using the memory, we're wanting to see the NON-Microsoft DLLs loaded under that svchost.exe

"No, the svchost.exe process is using all the memory." Using Process Explorer, check that svchost.exe process's DLL list...does it contain antivirus or software firewall DLLs? (Those are often memory-killers when uTorrent is running.)

newuzer, does Process Explorer and/or Task Manage show uTorrent as using all that memory?

Above my chart, there's this: These links explains my chart further: http://forum.utorrent.com/viewtopic.php?pid=422150#p422150 http://forum.utorrent.com/viewtopic.php?pid=445688#p445688

Either your upload speed doesn't go any higher even when you raise the upload speed limit...or worse, it actually FALLS when you raise the upload speed limit further.

50 mbit/sec upload settings. Maybe even increase upload speed limit considerably -- you'll have to test if/when that fails to go any higher.

spidermonkey666, that would depend on your ISP's bandwidth quotas more than linespeeds... Are you limited on how much you can upload per day? If so, you'll have to use much lower settings or use Scheduler and/or Transfer Cap.

Preferences, BitTorrent ...disable/uncheck Bandwidth Management and uTorrent will quit making new uTP peer/seed connections -- though it won't disconnect any existing ones until you stop the torrent or restart uTorrent. Recheck Bandwidth Management and uTorrent will immediately start making new uTP peer/seed connections.

Possibly 2 computers on the same LAN running uTorrent...which might explain different ports and different percentages complete.

You'd think after a couple years of this that someone else would make mention of that... The caption is directly underneath the chart. The "These links explains my chart further:" are right above it. Add more text to fix this problem? (yes/no)

Preferences, BitTorrent...uncheck Bandwidth Management which then also disables uTP. (You may need to restart torrents and/or uTorrent to get existing uTP peer/seed connections to break.)

That looks correct, but if your ISP throttles BitTorrent traffic then uTorrent may not be able to reach 72 KiloBYTES/second upload speed. If you're trying to download a 1+ GB torrent that has more peers than seeds and 72 KB/sec upload speed max isn't reached then you may be being throttled or have other problems (1st link in my signature for that.)

uTorrent will start more torrents if some of the 30 aren't active. The point is to not divide the upload speed so thinly that each peers downloading from you get <5 KB/sec. While only seeding, you also don't need very many connections per torrent. Even 10 will do.

http://forum.utorrent.com/viewtopic.php?id=57989 PEX - is there a bug with IPv6

SkyHi said, "when I have the "bandwidth management" enabled and seed, those who get connected with me through uTP don't download anything from me. Those with tcp do." Part of that may be due to a bug in uTorrent's uTP speed controls. It'll be fixed.

Make a new post with details asked for by 1st link in my signature in the Speed Problems. Hard to help without more info.

Maybe this will help then?: http://www.utorrent.com/documentation/beginners-guide

Rather than having uTorrent "guess" what local is, via new complex frameworks bolted into the protocol...or making broadcast messages across both the local LAN and a hop or 2 above it. ...Let's have access to what already exists. Better 2-tier performance from local/internet could become possible if we could define what "local" ranges are. In short, editing the internal LAN list. Ideally, we'd even have to set the speed max...as it may not be prudent to go as fast as the interface will bear even with uTP.