New Transmission 2.84 add-on for ReadyNAS Duo/NV+ (sparc)

Yup, that connects. I've been enabling and disabling upnp and when it's on, I see the specified port and IP in my router's upnp list. From what I can tell, things just suddenly stopped working a week or so ago with no known changed on my part. I can ping Internet domains from the Duo and I see Transmission listening on the specified port too. Really perplexed!

Did you try rebooting the NAS?

Yup. Rebooted NAS, restarted router, and Uninstalled and reinstalled the Transmission add-on. I'm really at a loss. I'm ready to try another client, if there is one. A desktop-based Transmission clientclient worked fine.

still struggling with this ... all inbound connections seem to connect, I can ping Internet domains from the NAS (via ssh), and i can see in my router that there are inbound connections to my NAS IP and Transmission listen port that are in TIME_WAIT or UNREPLIED state. Further, if I look at outbound connections from my NAS I see outbound connection to 239.255.255.250 in UNREPLIED state. Internet search seems to indicate this is related to UPnP. I have to wonder if some UPnP "test' is failing, thus making Transmission think the port is closed, and it won't respond to inbound connections. There are several other connections in UNREPLIED state as well, so I feel like the connections are coming in, they're getting to the NAS, it's just not sending any data back. So perplexing. Any other ideas, anyone?

addict wrote:

still struggling with this ... all inbound connections seem to connect, I can ping Internet domains from the NAS (via ssh), and i can see in my router that there are inbound connections to my NAS IP and Transmission listen port that are in TIME_WAIT or UNREPLIED state. Further, if I look at outbound connections from my NAS I see outbound connection to 239.255.255.250 in UNREPLIED state. Internet search seems to indicate this is related to UPnP. I have to wonder if some UPnP "test' is failing, thus making Transmission think the port is closed, and it won't respond to inbound connections. There are several other connections in UNREPLIED state as well, so I feel like the connections are coming in, they're getting to the NAS, it's just not sending any data back. So perplexing. Any other ideas, anyone?

What bit-torrent ports are you forwarding from router to NAS? And I hope you have reserved an IP address to the NAS MAC address.

I have these ports forwarded to my NAS: 51413, 6881-6889

I'm currently using Upnp With no specific ports set up for forwarding (as per instructions on the Transmission wiki). I _had_ been forwarding just 1 port to the static IP of my NAS, not using UPnP, and disabling random port use (thus, not forwarding any defined range of ports)

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!

oddly, there are no tracker errors, just Transmission showing Port Closed and no peers connected. I'll disable UPnP, go back to static routing, and try the same set of ports you used to see if it does anything. Thank You for replying!

Just found another user experiencing the exact same symptoms using version 2.84 of Transmission on his Synology NAS. It started May 30, 2016, same as me. What could be going on here!?

I am also suffering from this issue. I have been for about a week, but I had things so screwed up from my deb-package making attempts that I didn't worry much about it. Just finished a full and complete factory reset after backing up my data, installed the transmission 2.84 addon and am now showing the port as closed. uPnP is enabled on the router, and no peers on any torrent. The NAS has internet connectivity, tested as good.