BakaBT > Need Help? Ask Here

What to do in this situation? [solved]

(1/2) > >>

ripcode:
What to do in this situation?

its happening to me everyday (click to show/hide)


Al_Sleeper:
Have you considered changing your ISP?

ripcode:
sorry
but i cant.

is  there any prob with my isp?

Al_Sleeper:
Or your system.

datora:
.
I'm not fully clear on what the "situation" is.

The first two columns appear to be torrent size, then amount downloaded.  They are all seeding, then ratio(?) is infinite on all and then the numbers of seeders and the numbers of leechers.

So, are you saying that they are not seeding?  No upload to leechers is taking place?

And then, the tracker is offline for the selected torrent.  I may assume that all of your torrents are offline?  The three stats marked "not allowed" are supposed to have that status; all BBT torrents don't allow those protocols.

So, this "offline" status is your question?  Is it always like that, or does it re-establish & then go offline again?  I think you're using utorrent?  On Windows (7) probably?

It would be normal to see torrents go offline, then reaquire.  Occasionally.  It would not be normal to see them go offline often and for long periods of time.  I get offline status on some of my torrents every day, but usually its about 5 or 10 out of 60 or 80 running, and it usually clears up withing ten to twenty minutes.

Is your open port configured properly?  Is your connection through a router?  Is your torrenting client using the same port always, or changing it every time you restart?  Do you restart often, or do you leave your client running 24/7?

I also run Peerblock, which sometimes interferes with torrents.  However, it only seemed to mess with bakaBT torrents once for me about a year ago until I tracked it down and whitelisted the BBT domains.  It does, however, regularly cause issues with other trackers; even so, it usually allows torrenting to continue, even though at less than optimum bandwidth use (probably via peer exchange).

Navigation

[0] Message Index

[#] Next page

Go to full version