kinda an old topic but I'm bored, don't wanna read/code, and its 5 am
you guys are probably talking about the connection_problem(url,conection_refused) thing (I'm certain thats not the exact way it looks but you get the idea right?) anyway, this has to do with bandwidth limiting techniques the trackers use, which is limiting the number of connections in certian blocks of time. Unfortanely some trackers set this number relatively low (not there fault, I'm sure its all they can spare for tracking) and with other ppl on the tracker it gets very hard to connect, infact with no intervention it will sometimes just stay that way. Resolution: hammer* the tracker. I already know that sounds bad but theres no other way to get past it sometimes. As soon as you connect to it once you will get some vital info (ips to connect to) and your peers will provide some ips they have cached as well (if I'm not mistaken) at this point of just seeing 1 other peer or so, you can stop hammering it and if theres any other ppl on the torrent, things should take off from there.
* by hammering I mean you should do a manual announce to the tracker