Jump to content

Sending out bad pieces (hashfails).


leshafunk

Recommended Posts

Posted

Recently I have noticed I have seeding problem - often I'm constantly sending out bad pieces which fail hash check at leecher's side. A couple of kind leechers on a private tracker informed me about the problem and helped with further tests.

Of course the data is not corrupted, because after leechers reset bans they are able to complete download 100%.

After reading FAQs and forums I still have no idea where to look for the source of this problems.

My set-up:

uTorrent 2.04 (fixed custom port no.) - WinXp with correctly set-up native firewall (exclusion for uTorrent) - static local IP - wired connection to D-Link DI-824 router, port forwarding set up correctly - PPoE connection 18 Mbit/s symmetrical (100 Mbit/s for local connections, so when there is a local peer I can get 4-5 MByte/s) - static external IP.

Something ain't right there.

Steps already taken but did not help:

- uTorrent upgraded to 2.04

- outgoing Protocol Encryption - enabled

- disabled UPnP and NAT-PMP (as everything is static)

- Windows native firewall exception rule removed and created again.

Also Glasnost test didn't find any problems with ISP throttling BitTorrent traffic.

Please provide an advice what else I should check to eliminate the problem.

Posted
Uncheck the 2nd box for one...on the disk cache page.

How much could be sufficient cache size?

I can see 32 MB suggested, but that's a joke nowadays, e.g. when piece sizes are 4 MB.

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...