Port is closed even when forwarded in router

Ask for help and report issues with the Mac OS X version of Transmission
zenjim
Posts: 6
Joined: Thu Aug 04, 2016 3:02 pm

Port is closed even when forwarded in router

Postby zenjim » Wed May 10, 2017 2:22 am

Hi

I'm having a problem with Transmission saying Port is closed even though I have it forwarded in my router.
Port in transmission is set to 64959
Port forwarded in router is 64959 with Private UDP port set to 10 and Private TCP port set to 11.
UPnP is enabled on router. tried it with and without this enabled, same result.
Firewall has transmission set to allow incoming connections
Transmission is set to Automatically map port, but gets same result.
MacOS is 10.12.4
Transmission is 2.92
Router is latest Airport Extreme running v7.7.8.

below is debug log:

2017-05-10 01:36:29 +0000 port-forwarding.c:180 [Info] Port Forwarding: Stopped
2017-05-10 01:36:29 +0000 natpmp.c:70 [Info] Port Forwarding (NAT-PMP): sendnewportmappingrequest succeeded (12)
2017-05-10 01:36:29 +0000 port-forwarding.c:92 [Info] Port Forwarding: State changed from "Forwarded" to "Stopping"
2017-05-10 01:36:38 +0000 tr-dht.c:537 [Debug] The+Flash+2014+S03E21+HDTV+x264+SVA: Learned 100 IPv4 peers from DHT
2017-05-10 01:36:39 +0000 natpmp.c:70 [Info] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
2017-05-10 01:36:39 +0000 natpmp.c:70 [Info] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
2017-05-10 01:36:39 +0000 upnp.c:239 [Debug] Port Forwarding (UPnP): UPNP_GetValidIGD failed (errno 0 - Undefined error: 0)
2017-05-10 01:36:39 +0000 upnp.c:242 [Debug] Port Forwarding (UPnP): If your router supports UPnP, please make sure UPnP is enabled!
2017-05-10 01:36:39 +0000 port-forwarding.c:92 [Info] Port Forwarding: State changed from "Not forwarded" to "Starting"
2017-05-10 01:36:47 +0000 natpmp.c:70 [Info] Port Forwarding (NAT-PMP): readnatpmpresponseorretry succeeded (0)
2017-05-10 01:36:47 +0000 natpmp.c:138 [Info] Port Forwarding (NAT-PMP): Found public address "<deleted for my protection>"
2017-05-10 01:36:47 +0000 natpmp.c:70 [Info] Port Forwarding (NAT-PMP): sendnewportmappingrequest succeeded (12)
2017-05-10 01:36:48 +0000 natpmp.c:70 [Info] Port Forwarding (NAT-PMP): readnatpmpresponseorretry succeeded (0)
2017-05-10 01:36:48 +0000 natpmp.c:218 [Info] Port Forwarding (NAT-PMP): Port 64959 forwarded successfully
2017-05-10 01:36:48 +0000 port-forwarding.c:92 [Info] Port Forwarding: State changed from "Starting" to "Forwarded"
2017-05-10 01:37:19 +0000 tr-dht.c:537 [Debug] NCIS+S14E23+HDTV+x264+SVA: Learned 100 IPv4 peers from DHT

zenjim
Posts: 6
Joined: Thu Aug 04, 2016 3:02 pm

Re: Port is closed even when forwarded in router

Postby zenjim » Sat Aug 05, 2017 11:02 pm

3 months and no reply???

darmok
Posts: 12
Joined: Tue Oct 16, 2007 9:14 pm
Location: New Jersey, USA

Re: Port is closed even when forwarded in router

Postby darmok » Tue Aug 29, 2017 9:16 pm

zenjim wrote:problem with Transmission saying Port is closed even though I have it forwarded in my router.
Port in transmission is set to 64959
Port forwarded in router is 64959 with Private UDP port set to 10 and Private TCP port set to 11.

Forward incoming port 64959 to port 64959.

Punch a hole thru your firewall and manually tell Transmission its number (so Transmission can tell peers which port to use). You do not want to remap the hole to some low port, that's already used by some other service.

HTH,
- Dan.


Return to “Mac Support”