Switeck

And the weird thing about PEX message flood ban...many/most seem to be other uTorrent v2.x clients.

How can BitTorrent fix a line issue?!

Same -- missing icon in taskbar. A workaround might be to use BOSS key.

I am using Win XP SP3 32bit and dates and times are 1970 and wrong.

After such a big mistake, it would have been much better to increase the official version to v2.0.5.Because otherwise trackers either ban all of v2.0.4 or they have to ban by build number.

The text could be reworded so the alternate upload limit is "when only seeding", but that doesn't mean it's illogical the way it is.

What about if a seed/peer quickly disconnects and reconnects? Couldn't it (foolishly?) send a new PEX message?

It's not uTorrent, as DWK was hinting at, it's almost certainly SOMETHING ELSE. You'll need to do some troubleshooting to find what hostile software on your computer is preventing uTorrent from running correctly.

That feature can be VERY hard on seeds though if lots of people do it. The first file in a series can get requested over-and-over again from the seeds, far more often than all the other files. The seed could leave with 5:1 ratio and have never uploaded the last file/s.

Katrasiz, others have reported problems with Verizon: http://forum.utorrent.com/viewtopic.php?pid=432674#p432674

Wouldn't that be down to 10 from 50?

So the "Disconnect: PEX message flood" bug (which shows up in uTorrent's logger window/tab if errors are monitored) has not been fixed? (This bug affects uTorrent v2.0.4, v2.2, v2.2.1, and v3.0)

califab, you may only have a tiny fraction of the shared internet connection AND have BitTorrent traffic blocked/throttled in multiple ways at multiple locations. Conservative speed settings alone won't help. 1st and 3rd links in my signature. Also try rafi's uTorrent Guide: http://forum.utorrent.com/viewtopic.php?id=74820 ...Many blocking methods are too thorough to be "defeated", because they block ALL unknown traffic.

Resolve IPs (if watching Peers window/tab), DHT, half open outgoing connections, bt.connect_speed, incoming connections, etc...all add up.

They're not sure if the secret changes are running stable, so uTorrent v2.2 is not set up to auto-update just yet. If there's no major reports of problems with uT v2.2 it will be on auto-update probably within a week or 2. ...That is preferable to having millions of people "upgrading" to a disastrously buggy version like has happened in the recent past even with earlier v2.0.4 builds.