Broken Port Forwarding detection
Broken Port Forwarding detection
Hello,
I have manually confirmed that my port forward is working correctly*, but Transmission still reports that the port is closed. I'm running Mac OS X version 2.75 (13665), which the app tells me is the latest version.
Is there a way to fix the detection?
Does it matter - with the detection failing, is Transmission telling other clients not to bother trying to initiate connections to me?
* I manually verified connectivity by running netcat on my mac on the port I'm using, and then ssh-ing to a public server and telnetting back to that port on my mac. The connection was established, and whatever gunk I typed into the telnet session came out of netcat on my mac.
Thanks in advance for any help!
**edit** In case it wasn't already obvious from my above post, this is with manual port forwarding, not upnp or nat-pmp. I explicitly manually forwarded port 36802 (and also 36804) on my Airport Extreme to my mac's current local DHCP IP. My Airport Extreme is running the latest software, and I have hard power-cycled it and rebooted my mac too.
**edit 2x** - corrected Airport reference to both be Airport Extreme
I have manually confirmed that my port forward is working correctly*, but Transmission still reports that the port is closed. I'm running Mac OS X version 2.75 (13665), which the app tells me is the latest version.
Is there a way to fix the detection?
Does it matter - with the detection failing, is Transmission telling other clients not to bother trying to initiate connections to me?
* I manually verified connectivity by running netcat on my mac on the port I'm using, and then ssh-ing to a public server and telnetting back to that port on my mac. The connection was established, and whatever gunk I typed into the telnet session came out of netcat on my mac.
Thanks in advance for any help!
**edit** In case it wasn't already obvious from my above post, this is with manual port forwarding, not upnp or nat-pmp. I explicitly manually forwarded port 36802 (and also 36804) on my Airport Extreme to my mac's current local DHCP IP. My Airport Extreme is running the latest software, and I have hard power-cycled it and rebooted my mac too.
**edit 2x** - corrected Airport reference to both be Airport Extreme
Last edited by leechb8 on Thu Dec 27, 2012 4:30 am, edited 1 time in total.
Re: Broken Port Forwarding detection
There is only one router, it's an Airport Extreme. There is also an Airport Express but it is in wireless extension mode, it is not operating at the IP layer at all.
Yes, I have T set to the port that I'm forwarding on the Extreme. I have tried several ports actually an in each case I updated the Extreme and T together to specify matching ports.
I also tried going directly to the cable modem, no protection whatsoever (for a few minutes just to test this). I still couldn't get T to recognize an open port. I tried canyouseeme.org and it confirmed that the port I have T set to is open.
Yes, I have T set to the port that I'm forwarding on the Extreme. I have tried several ports actually an in each case I updated the Extreme and T together to specify matching ports.
I also tried going directly to the cable modem, no protection whatsoever (for a few minutes just to test this). I still couldn't get T to recognize an open port. I tried canyouseeme.org and it confirmed that the port I have T set to is open.
-
- Posts: 1
- Joined: Thu Dec 27, 2012 8:36 pm
Re: Broken Port Forwarding detection
I'm having the same problem with 2.75. I check my forwarding status every couple of days, or if my upload speed seems poor just incase my router decided to give me a new IP. Even DMZ with firewall off is still showing "port is closed". Independent verification on port checking sites show that the port is open. No sure whats up on Transmission's end.
Re: Broken Port Forwarding detection
Same here, it was working fine until now. Port closed on transmission 2.71 and 2.73 on DNS 323
Re: Broken Port Forwarding detection
I have same error with ports.
Re: Broken Port Forwarding detection
I'm having the same problem, various website port checkers show my port as open, but Transmission is showing it closed for a few days now. I've tried manually opening the port, as well as the Transmission's "Randomize port on launch" function. Either way Transmission has been consistently showing it closed for a couple of days now, but other port checkers show it open.
I'm downloading an uploading fine, so I guess it's just a problem with Transmission ???
Using Transmission v 2.75 and Mac OS X 10.6.8 on a Mac Mini Aluminum 2010. Firewall is on, Transmission is set to allow incoming connections in the Firewall exceptions area. Never had a problem before. I have UpNP turned on in my Ubee/Charter wireless router/cable modem.
I'm downloading an uploading fine, so I guess it's just a problem with Transmission ???
Using Transmission v 2.75 and Mac OS X 10.6.8 on a Mac Mini Aluminum 2010. Firewall is on, Transmission is set to allow incoming connections in the Firewall exceptions area. Never had a problem before. I have UpNP turned on in my Ubee/Charter wireless router/cable modem.
-
- Posts: 4
- Joined: Thu Jul 17, 2008 11:19 am
Re: Broken Port Forwarding detection
Same problem here, canyouseeme.org and grc.com report the port as open and DL/UL speeds seem fine, but Transmission shows that it's closed. Transmission 2.75, Mac OS X 10.8.2
Re: Broken Port Forwarding detection
Same problem here, Transmission 2.75 and OS X 10.8.2.
Re: Broken Port Forwarding detection
Same problem. Transmission 2.75 and OS X 10.8.2. I tried to connect directly to cable moden and the problem persist. Other clients like uTorrent works fine.
Re: Broken Port Forwarding detection
same here w/ 2.75 & 10.6.8. http://canyouseeme.org/ shows my selected port is open, but T tells me it's closed.
Re: Broken Port Forwarding detection
Same damn red dot on transmission 2.75 on MacOSX 10.6.8.
I have port forwarded successfully and I am visible on Canyouseeme.org but not for Transmission....and speed is slow now.

I have port forwarded successfully and I am visible on Canyouseeme.org but not for Transmission....and speed is slow now.


Re: Broken Port Forwarding detection
Same situation here, since a couple of days...
Tried 2.73, same thing.
Tried 2.73, same thing.
Re: Broken Port Forwarding detection
Looks like it's a problem with the portcheck server.
Re: Broken Port Forwarding detection
Does this have an impact on the download speed? Because as far as I can see my Transmission download performances have drastically gone down since this problem popped out...
Re: Broken Port Forwarding detection
one more victim! Since a couple of days, suddenly Trasmission see the port closed. Canyouseeme or any other program or check see it open!
already updated at last version 2.73 and no firewall enabled...

already updated at last version 2.73 and no firewall enabled...


