Not able to connect to trackers/dht and unable to get shows?

all of our release (n.b. vtv and mvgroup make their own torrents) only contain udp based trackers
and dht. now, if your client does not support udp trackers correctly, or does not have dht, then you
will not be able to connect and get any peer information. it is also known that some vpn services do
not handle udp correctly, and it is suggested you contact them and get them to fix the issue.

here is a list of the trackers we add to our torrents:

udp://tracker.openbittorrent.com:80
udp://tracker.publicbt.com:80
udp://tracker.istole.it:80
udp://tracker.ccc.de:80
dht://

so again, our torrents are working fine, and the issue is with the clients not supporting these
trackers properly.

hey novaking - i guess this is why i can't download anything anymore - all that i get is a media play telling
me it can't play the file i am trying to download (this only started a couple of months ago) but i'm not
technological enough to know what it means for fixing this problem. some assistance would be much
appreciated.
cheers
lostincoburg

novaking,

for those of us who use clients that do not properly handle udp it would be really nice to have at
least one valid http tracker in each release. i notice some of your releases from some sources have
an openbittorrent http tracker, but that one never seems to work.

we use these clients with broken udp handling for other valid reasons otherwise we would upgrade and
fix it. is it really that big of a deal to have a single http tracker in the releases? many of us
use the rss feeds to auto d/l stuff, but if we have to manually add other trackers to each release
then it really degrades the ease of use of the auto setup.

maybe i'm missing something...

thanks for having this site. just hoping enough people would benefit from my suggestion that a
slight change could happen.

cromag

i would like to know what these "valid reasons" are. if you mention private trackers, then i must
inform you that when a private flag is set on a torrent, dht is turned off for that torrent. if
there is some other obscure reason why you can not use a client that properly supports udp, then i
must apologise now as this is something that will not be changing back.

i don't know about anyone else, but i use a privately configured version of utorrent that runs over
an ssh connection. this version of utorrent does not handle udp properly. i am not using private
trackers. i have always been using the eztv torrents without problem until recently. now that they
only contain udp trackers the eztv torrents have become less useful. i understand that the proper
solution would be for the provider of my custom configured utorrent client to upgrade to a newer
version of utorrent, but until that happens i (we ) are stuck between a rock and hard place between
eztv changes and lack of changes of our client.

i understand you not changing back. i was just asking in case it was easy to keep the http trackers
for a while. i do not understand everything about what you do and i understand if there is a reason
to abandon them (http) that you would not change back just for me.

i will continue to hound my client supplier to update their end.

thanks for responding.

it takes now for some about 3 days for ppl to now seed the new udp trackers due to the lost of the old
http trackers which most of the utorrent users use. does bittorrent work better or do we wait for
utorrent to catch up and would the peer/seed numbers return to a useable number i guess time will tell

mit669

ut supports udp, has for ages

may i suggest to the ppl who are having this problem .... simply change the prefix of the desired
tracker to http in the properties of the torrent and it should connect. make sure your dht and peer
exchange are also enabled.

hello everyone. i'm am an azureus user, and have been for a few years. i've also been a fan of
eztv releases ever since i started downloading tv shows. i saw this problem recently and it affects
me greatly for 1 major reason. i know az vuze supports udp. the problem i'm having is that i have
to use btguard to download my torrents for a couple reasons.
1) because my isp keeps sending me emails about torrents i get from eztv, so i have to go through a
proxy like btguard.
2) right now i'm stationed in afghanistan...and all the internet here is blocked by
websense...including torrents. i found that using btguard is the only way i can torrent to get my
shows out here, but they don't support and udp trackers at all. most proxy servers don't. why? i
have no clue, but there is no other option.

so as of late, i've been having to add http trackers to get these torrents to work. if i can add
them and the torrents work, why can't you guys add them until udp is a more standard protocol used?

exactly.

well, i'm using transmission (for mac) and it does support udp. but for the past week, no matter
which torrent i use, i can't download any shows; nothing ever starts. if i look in the view>show
inspector window, i see this for the tracker:

http://tracker.openbittorrent.com/announce

and i can't change that. so, either the torrent has a udp tracker than automatically changes to http
when opened by the client, or it's an http tracker that doesn't work anyway.

these are the shows i'm currently trying to download: law & order la s01e15 (349.7 mb), and law &
order: criminal intent s10e03 (350.1 mb). if others using transmission on the mac can try these and
tell me whether or not it works for you, that would be helpful, as well as anything that you're
doing to make it work, and how you did it. i'm running os x 10.4.11, and i know transmission for os
x 10.5 or higher does have other features not available in my version of the client.

but so far, i've got nothing to show for my waiting.

salmonella,

you're completely correct.

numerous people on here have confirmed that the problem does not lie with the users. despite what
site admins say here, the problem is with this site...

actually, i am sorry, but it lies with uneducated users that cannot read solutions or instructions

5 minutes to correctly set up your client, static ip, and portforward your router

okay scifi3001, if you really believe that users are so stupid, then you be the man and tell us all
how to do it with all the various bittorrent clients out there, and that includes transmission for
mac os x.

when i could download some things last week (including the two shows i currently can't download),
and nothing has changed on my client or my system since then, it points directly to an issue with
the torrents, not the user or the client.

insulting users by telling them they're stupid when there is no evidence to support it is the height
of arrogance. it's eztv that decided to change the torrent trackers without seeking input or giving
advance notice to users, so the fault lies squarely with you guys (or gals). and when they don't
work you dismiss their problems as being their fault. keeping it classy, aren't you?

so, explain it to us, you all-knowing guru, and be very specific for each client.

well, this was a decision we decided to make, we knew some people would be using shitty old clients,
and we knew some vpns/proxies don't handle udp forwarding. of course you are welcome to add http
trackers yourself, we are not stopping you. but we will continue to only provide dht/udp trackers...
we are looking towards the future, and we apologises if this affects some people in the process.
things will only get better and you guys wouldn't even remember what this was even about.

again, we will not be putting http trackers back into our releases. so asking us to do so is simply
wasting your time.