BitComet affected more than uTorrent?

It seems my local ISP packet shaper is able to somehow affect, block/filter or slowdown most (but not all) of my BitComet connections (I have enabled ENCRYPTION always). Now I have so many downloads stuck (many at 77%+ to 90%+) because downloads speeds are like 0KB/s~1KB/s (total downloads!!) most of the time! 2KB/s~5KB/s seems to come and go randomly (for very short periods). Before this I can get 20KB/s to 38KB/s easily. :dots:

With uTorrent I can get around 10KB/s at least! (ie. starting to use more uTorrent now). :slight_smile:

Wondering what’s going on actually. Is the packet shapers like NetEnforcer able to recognize BitComet-specific protocol (even encrypted ones) or connections? :unsure:

To prove my point, check the attached images.

Picture 1 = Seems more downloads from uTorrent peers than BitComet ones!

Picture 2 and 3 = BitComet have 7 downloads (all have seeds), UTorrent have 1 download (1 seed only)

/post-9087-1159237762.png" rel=“”>

/post-9087-1159237778.png" rel=“”>

/post-9087-1159237794.png" rel=“”>

Your pictures didn’t come across too well.

The protocols used are identical. If a client deviates very much at all, it can no longer communicate. Issues like this are usually configuration problems.

µTorrent and BC use the same PE (Protocol Encryption) & DHT.