Stop BitTorrent from Killing Your Internet Connection

Many popular BitTorrent clients such as uTorrent/BitTorrent, BitComet and Vuze can work right out of the box. Download, install, load a torrent file and it’ll start downloading, provided any needed ports are forwarded correctly. If you don’t tweak the configurations, most probably it’ll take you longer to complete downloading the torrent because the default configuration might not be very well optimized for your router or internet connection.

A slow to finish downloading game, movie or file from a torrent is not really a big problem. The biggest problem you’ll probably encounter is when someone else is on the network and your computer is downloading a torrent. Quite often all of sudden the internet connection will seem like it’s been cut off as if someone is using NetCut and there are problems browsing the web, Skype or your messenger program disconnects etc. Pinging the router could well give a “Request time out” error message.

This problem happens both with a modem and router. To get back the connection, you might need to disconnect and reconnect the internet connection, restart the router or even reboot the computer if the problem is really bad. Restarting the router is not a good solution because when the torrent detects a connection and starts downloading, the connection gets killed again.

There are ways to configure a torrent client such as uTorrent, BitComet, Bitfrost or Vuze so that if you’re having similar problems, your internet won’t get disconnected while downloading torrents.

This happens mainly because there is a large number of connections that BitTorrent utilizes is stressing out your router/modem. The default settings in a BitTorrent client are sometimes providing more connections than some modems/routers can handle. Since many of us are actually using the free and cheap modems or routers such as the Riger DB108-WL provided by our ISP , we have to lower the global connections in the BitTorrent Client.

Change the Connections in BitComet

1. Go to Tools and select Options (or press CTRL+P) to bring up the preference options.

2. Go to Advanced and click on “network.max_connections”.

3. Change the value from 0 (unlimited) to a more usable connection number (100) in the “Value:” box below, then click Apply.

BitComet network.max_connections

Change the Connections in Frostwire

1. Click on the Tools menu and go to Options, expand the Bittorrent tree and select Advanced.

2. Change the value in “Global maximum number of connections” to your desired vale, thankfully the default isn’t set that high to start with at 100.

frostwire global maximum number of connections

You’ll find more connection setting for some popular torrent clients on Page 2.

67 Comments - Write a Comment

  1. Luks 3 months ago
  2. Max 3 months ago
  3. Shaunny 5 months ago
  4. seeker9969 9 months ago
  5. Drikon 11 months ago
  6. Jim 1 year ago
  7. Zaphod Beeblebrox 2 years ago
  8. Jared 2 years ago
  9. Charlie 2 years ago
  10. Kommicky 3 years ago
  11. dave9 4 years ago
  12. Det 4 years ago
  13. Paritosh Bhatia 4 years ago
  14. mzhop 5 years ago
  15. Kishu 5 years ago
  16. Momir Peh 5 years ago
  17. patrik 5 years ago
  18. RK 5 years ago
  19. SternGuy 5 years ago
  20. Anonymous 5 years ago
  21. Yannick 6 years ago
  22. Jose 6 years ago
  23. blinky 6 years ago
  24. Tom v 6 years ago
  25. Jacob 6 years ago
  26. KingBubba 6 years ago
  27. Bahamut 6 years ago
  28. Svetoslav 6 years ago
  29. nelsonlee 7 years ago
  30. asldjfal 7 years ago
  31. Simon 7 years ago
  32. Will 7 years ago
  33. Beninu Andersen 7 years ago
  34. Thad McGuinness 7 years ago
  35. Qusay 7 years ago
  36. mario 7 years ago
  37. Arunex 8 years ago
  38. Guest 8 years ago
  39. Lek 9 years ago
  40. Aaron 10 years ago
  41. Andrew 10 years ago
  42. rashidah 10 years ago
  43. James Miller 10 years ago
  44. LOL 10 years ago
  45. Lakshman 10 years ago
  46. seicean 10 years ago
  47. RWB 10 years ago
  48. Lou 10 years ago
  49. ChrisV 11 years ago
  50. vrotom 11 years ago
  51. ken 11 years ago
  52. oogleman 11 years ago
  53. Nick 11 years ago
  54. Rose 11 years ago
  55. king 11 years ago
  56. kilikopele 11 years ago
  57. Rye-Guy 11 years ago
  58. nick 12 years ago
  59. Clare Martin 12 years ago
  60. Russ 12 years ago
  61. asterix 12 years ago
  62. xcroz 13 years ago
  63. Reza 13 years ago
  64. Greg 13 years ago
  65. phreaq 13 years ago
  66. anoop 13 years ago
  67. Ralph 13 years ago

Leave a Reply

Your email address will not be published. Required fields are marked *

Note: Your comment is subject to approval. Read our Terms of Use. If you are seeking additional information on this article, please contact us directly.