NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
tarobun
Nov 24, 2012Tutor
New Transmission 2.84 add-on for ReadyNAS Duo/NV+ (sparc)
This is a newly compiled version for the Duo straight from source. It has been configured with "--disable-nls --enable-lightweight --enable-utp" and the default web interface port of 9091. If it do...
Mr_B
Jun 06, 2015Guide
I've been ransacking my memory, and i know i have set my transmission clients to static ports and manually configured them in the firewall, since some torrent sites had the habit of claiming that i was "un-connectable" at the uPnP specified port. But while some trackers reported this, others never saw an issue, so i believe it was actually on the tracker-end this issue existed. It also never resolved those trackers, they still think my port isn't open. In the end i just reported it to the admins, who made sure the tracker didn't pay attention to that, and that the peers gets my info regardless. What i'm aiming at... Are you sure your "checking" it with a working tool?
Also, "could not connect to tracker" shouldn't have anything to do with your port forward setup. the port you set is nothing but active mode transfers. Thats peer to peer. The tracker communication doesn't need a incoming port configured. It just expects that outgoing traffic is allowed, and the tracker has the "active" role in the conversation. Meaning unless your NAS is blocked from accessing the net, it's not on your end. The tracker simply doesn't respond. You can be blocked / banned, or, the tracker is blocked / banned, in your gateway/firewall, or possibly on a ISP level.
Anyway, the description of the error, and the suggested problem doesn't seam to add up. Figure out whats actually broken, and start looking at it from that end, and it should be easier to provide an answer...
B!
Also, "could not connect to tracker" shouldn't have anything to do with your port forward setup. the port you set is nothing but active mode transfers. Thats peer to peer. The tracker communication doesn't need a incoming port configured. It just expects that outgoing traffic is allowed, and the tracker has the "active" role in the conversation. Meaning unless your NAS is blocked from accessing the net, it's not on your end. The tracker simply doesn't respond. You can be blocked / banned, or, the tracker is blocked / banned, in your gateway/firewall, or possibly on a ISP level.
Anyway, the description of the error, and the suggested problem doesn't seam to add up. Figure out whats actually broken, and start looking at it from that end, and it should be easier to provide an answer...
B!
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!