Pipeless
Regular Member
The issues that I raised in this thread earlier in the year have returned, along with some other rather strange behaviour.
I've not been using Bittorrent much over the last two or three months but I've noticed the "connection closed by peer" phenomenom has become commonplace when I do use it. Last week, starting on Monday Nov 22, I began closely monitoring the situation and have built up a picture of what's going on.
Everything's pretty much the same as what's in the thread, above, except that I've replaced my old USB modem with a Netgear DG834G router to try and improve things. Utorrent ports have been forwarded correctly (as per this page); I have the green "tick" on the bottom bar which gives the message "Network OK, Your network connection is working as it should".
Last week, up to friday (inclusive) I started torrents in the afternoons (1pm to 3pm), all with lots of seeds, using a variety of sources/trackers. With only a single torrent in the queue, none failed immediately (i.e. giving a "connection closed by peer" report) but downloaded/uploaded well (if very slowly!) ...... until the trackers began to update themselves for the first time. After the update, they all failed, which reduces download speed to a trickle and stops uploading, for some reason. If a second (or more) torrent is added to the queue it fails immediately - no traffic whatsoever.
Strangely, Saturday 27th was OK ...... all went well with no problems. Sunday I didn't use Bittorrent.
Yesterday, back to torrent failures. As I write today, same thing.
The "added twist" is that at 23:00 Hours exactly - and this has been the case since I've began monitoring - all queued torrents suddenly spring back to life. When the trackers update themselves, or if I can update them manually, the "connection closed by peer" message disappears and upload/download traffic resumes at a far better speed.
In a nutshell, Bittorrent has become virtually unusable before 11pm, because of 56K-modem-style speeds and the ongoing (!) "connection closed by peer" issue. I reckon Fast is charging waaaaaay too much for this kind of thing. What's going on?
I've not been using Bittorrent much over the last two or three months but I've noticed the "connection closed by peer" phenomenom has become commonplace when I do use it. Last week, starting on Monday Nov 22, I began closely monitoring the situation and have built up a picture of what's going on.
Everything's pretty much the same as what's in the thread, above, except that I've replaced my old USB modem with a Netgear DG834G router to try and improve things. Utorrent ports have been forwarded correctly (as per this page); I have the green "tick" on the bottom bar which gives the message "Network OK, Your network connection is working as it should".
Last week, up to friday (inclusive) I started torrents in the afternoons (1pm to 3pm), all with lots of seeds, using a variety of sources/trackers. With only a single torrent in the queue, none failed immediately (i.e. giving a "connection closed by peer" report) but downloaded/uploaded well (if very slowly!) ...... until the trackers began to update themselves for the first time. After the update, they all failed, which reduces download speed to a trickle and stops uploading, for some reason. If a second (or more) torrent is added to the queue it fails immediately - no traffic whatsoever.
Strangely, Saturday 27th was OK ...... all went well with no problems. Sunday I didn't use Bittorrent.
Yesterday, back to torrent failures. As I write today, same thing.
The "added twist" is that at 23:00 Hours exactly - and this has been the case since I've began monitoring - all queued torrents suddenly spring back to life. When the trackers update themselves, or if I can update them manually, the "connection closed by peer" message disappears and upload/download traffic resumes at a far better speed.
In a nutshell, Bittorrent has become virtually unusable before 11pm, because of 56K-modem-style speeds and the ongoing (!) "connection closed by peer" issue. I reckon Fast is charging waaaaaay too much for this kind of thing. What's going on?