ziggy17 Posted September 28, 2006 Share Posted September 28, 2006 Hi I have a bit of a problem I was using my BitComet fine when it all changed and now nothing will connect. All show Tracker Return xx Peers (where xx is > 0), but looks like 0/0[0/xx] in the Seed/Peer[All] column (again xx represents various numbers >0). I dont know what to do as all was working fine one day then next not at all. I am at Uni and so get my internet through their system, but my browser is unaffected! I did not change any settings, and all seem to be in order with the various suggestions on the forum. I even upgraded from 0.68 to 0.70 (after the issue occured) and so it is not due to old version or firewall block. Please help as this is the first issue I have had since starting to use BitComet 6 months ago. Oh I have also restarted my computer...so stuck for ideas. Thanks in advance Ziggy Link to comment Share on other sites More sharing options...
kluelos Posted September 29, 2006 Share Posted September 29, 2006 The problem may yet be (and sounds like) firewall block, if you have a software firewall. Rule it out, in any case: delete your firewall rule for BitComet, and re-create it. Don't forget to make it for UDP as well as TCP. Link to comment Share on other sites More sharing options...
ziggy17 Posted September 29, 2006 Author Share Posted September 29, 2006 Did that a couple of times as I say, and just checked both TCP and UDP, are set to permit all. More information, if I click on the trakers tab (bottom left) and while in all cases it does return >0 Peers, it also reads 'Can't Connect Tracker (10060)' or 'Can't Connect Tracker (10061)'. Dont know if that helps someone work out whats up!? I hope so. Thanks again Link to comment Share on other sites More sharing options...
dsacco Posted September 29, 2006 Share Posted September 29, 2006 i have the same problem. from yesterday night i cant connect with trackers. whats the problem? Thanks Link to comment Share on other sites More sharing options...
CuteSniper22 Posted September 30, 2006 Share Posted September 30, 2006 Did that a couple of times as I say, and just checked both TCP and UDP, are set to permit all. More information, if I click on the trakers tab (bottom left) and while in all cases it does return >0 Peers, it also reads 'Can't Connect Tracker (10060)' or 'Can't Connect Tracker (10061)'. Dont know if that helps someone work out whats up!? I hope so. Thanks again May be you share ur single port with two p2p software ? One p2p software only can use one port.. Can't share 2 with 1 port.... Link to comment Share on other sites More sharing options...
kluelos Posted September 30, 2006 Share Posted September 30, 2006 Ziggy, that's an entirely different issue, and one that you probably should have reported first. Always check the tracker for error messages. That 10060 error means you haven't be able to succesfully scrape the tracker -- it's too busy to respond -- so you haven't got its list of peers yet. Since you did GET a response from the tracker (even if it's just saying it's too busy) this removes the firewall issue, or at least postpones and redimensions it. The problem is usually cured by simply waiting. Your client will rescrape and eventually get a successful scrape. If this persists for a long time (an hour or so), try again later. If it persists for several days, the tracker has probably been effectively taken down. The numeric error codes are WinSock errors, which see. Some of them will tell you that you'll never connect to that tracker, so you won't be getting that torrent. Link to comment Share on other sites More sharing options...
ziggy17 Posted September 30, 2006 Author Share Posted September 30, 2006 Kluelos was spot on! It was just waiting... did take about 3/4 days, but i woke up this morning and I am downloading at 81KB/s now.... IDEAL!!! Thanks all for your responses, problem fixed Ziggy Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now