Jump to content

DreadWingKnight

Administrators
  • Posts

    43,283
  • Joined

  • Last visited

  • Days Won

    194

Everything posted by DreadWingKnight

  1. that's because vista blocked the c:\program files path.
  2. And yet our testers can't recreate the problem scenarios you're getting.
  3. No it doesn't. I run a tracker cluster and know that it continues on to the next tracker in the tier.
  4. http://wiki.depthstrike.com/index.php/P2P:Protocol:Specifications:Multitracker
  5. http://utorrent.com/faq.php#What_does_Download_Limited_in_the_status_bar_mean.3F Not a bug.
  6. You think very poorly. 1 word netstat
  7. No. Running that many torrents at a time will cause some to run at less than 1kbyte/sec. Torrents that are running at less than 1kbyte/sec aren't counted towards queue counts.
  8. Bitcomet is known to not play nice.
  9. What clients are the offenders running?
  10. Your requests aren't going to happen. BitTorrent is NOT a sequential downloading protocol. The bug is probably a wine bug relating to how directory lists are passed to the application.
  11. quertiy, what piece size are you trying to use?
  12. stop assuming something is wrong. do you have an apple brand router? if no, ignore nat-pmp errors.
  13. Why are you using 6881 for your port and how many torrents are you running at a time?
  14. The network health indicator in the status bar (the one next to the speed status,etc) has nothing to do with DHT other than its icon being next to the DHT status. It shows wether or not you're getting incoming peer connections. As long as you have incoming peer connections established, it's green. It doesn't attempt to contact a test server on its own at all.
  15. Nice of you to leave out the upload rate column krazyson.
  16. Maybe it's your software firewall being stupid. nVidia's chipset drivers also have a software firewall that is the actual cause of a disheartening number of memory leaks.
  17. Probably not. Probably the fault of your router rather than uTorrent. Are you manually forwarding?
  18. Exactly. Linksys routers refuse to forward to IP addresses within their DHCP range because they have no way of ensuring that the machine they're forwarding to will be the same every time. They may re-assign the IP address or other similar issues can come up.
  19. Linksys routers will simply refuse to forward to any IP within their dhcp range, be it statically assigned or not. Set your static IP outside of that range.
  20. Simple, you're forwarding to an IP within the router's DHCP range (which simply doesn't work with linksys routers). Set a static IP (according to portforward.com) to something outside of the router's dhcp range and try again.
  21. NAT-PMP is currently exclusive to Apple brand routers. That's why it doesn't work with yours.
  22. because only one is supposed to work at a time (if either will) NAT-PMP is currently apple-only
  23. So you can't UPnP or NAT-PMP. So what? Not being able to do either means nothing to wether or not you can download.
×
×
  • Create New...