Transmission port closed :(
Transmission port closed :(
Please help, I've tried port forwarding, disabling the firewall, nothing I've done is working.
- Attachments
-
- This is the screenshot of the log.
- Screen Shot 2013-06-28 at 12.23.55 PM.png (158.49 KiB) Viewed 10265 times
-
- Posts: 3
- Joined: Sun May 25, 2008 8:21 am
Re: Transmission port closed :(
Try to click "Randomize"? It helped for me when Transmission showed port 51413 to be closed after the latest update....
-
- Posts: 3
- Joined: Sun May 25, 2008 8:21 am
Re: Transmission port closed :(
That only seems to have helped temporarily. Since the latest update (to 2.80 (14103)), the port is now closing all the time.
I have not changed anything else in the set-up apart from downloading the latest Transmission update. Seems as if maybe I should have held off on that.....
I have not changed anything else in the set-up apart from downloading the latest Transmission update. Seems as if maybe I should have held off on that.....
Re: Transmission port closed :(
Was getting similar issues as well, thought it was router. Port was list closed, closed Transmission and re-opened it again and had it check port status which it listed as open now. However transfer speeds were awful. Downgraded back to previous version and transfer speeds jumped back to normal.
Re: Transmission port closed :(
I've tried reinstalling, randomizing the port and port forwarding, all of it doesn't work. :/x190 wrote:A restart/re-install/clean re-install can cure a multitude of ills for any program.closed Transmission and re-opened it again
This is where a clean install may have helped or it could simply be luck of the draw.However transfer speeds were awful. Downgraded back to previous version and transfer speeds jumped back to normal.
#1 Move the following folders/files to your Desktop for later disposal.
~/Library/Application Support/Transmission (.torrents can be found here and can be re-added to Transmission. Use "Move Data File To..." (enclosing folder) and "Verify Local Data" as necessary.)
~/Library/Preferences/org.m0k.transmission.LSSharedFileList.plist
~/Library/Preferences/org.m0k.transmission.plist (re-do Preferences after installation)
~/Library/Caches/org.m0k.transmission
"~" = your home folder.
http://osxdaily.com/2011/07/22/access-u ... os-x-lion/
#2 Trash the .app.
#3 D/l a fresh copy and re-install application.
http://www.transmissionbt.com/download/
Re: Transmission port closed :(
I clicked proceed and the instant uPnP Exposure Test. The result I got was "THE EQUIPMENT AT THE TARGET IP ADDRESS DID NOT RESPOND TO OUR UPnP PROBES! (That's good news!)"
-
- Posts: 552
- Joined: Sun Dec 13, 2009 10:44 pm
Re: Transmission port closed :(
Right, and that test is to see if your router is miss-configured by accepting uPnP calls from the general internet (which is a very bad thing). That part does not check if specific ports are open.chins96 wrote:I clicked proceed and the instant uPnP Exposure Test. The result I got was "THE EQUIPMENT AT THE TARGET IP ADDRESS DID NOT RESPOND TO OUR UPnP PROBES! (That's good news!)"
Re: Transmission port closed :(
Okay, sorry for the trouble, I don't really know how all of this works. Is this the one you're supposed to check?blacke4dawn wrote: Right, and that test is to see if your router is miss-configured by accepting uPnP calls from the general internet (which is a very bad thing). That part does not check if specific ports are open.
- Attachments
-
- Screen Shot 2013-07-07 at 5.06.12 PM.png (64.35 KiB) Viewed 10014 times
-
- Screen Shot 2013-07-07 at 5.06.03 PM.png (37.92 KiB) Viewed 10014 times
-
- Posts: 552
- Joined: Sun Dec 13, 2009 10:44 pm
Re: Transmission port closed :(
That looks to be a full comprehensive scan of the first 1056 ports, not enough to actually reach the ports Transmission uses.
On the page with the "GRC's instant UPnP Exposure Test" button you will have a input box slightly below it, enter the peer-port (51413 by default) there and then press "User Specified Custom Port Probe". That should do it.
Looking over your OP again makes question if this is needed at all. Not sure if it's been fixed now but Transmission's own routine to check if the port is open or not hasn't been that reliable.
On the page with the "GRC's instant UPnP Exposure Test" button you will have a input box slightly below it, enter the peer-port (51413 by default) there and then press "User Specified Custom Port Probe". That should do it.
Looking over your OP again makes question if this is needed at all. Not sure if it's been fixed now but Transmission's own routine to check if the port is open or not hasn't been that reliable.
Re: Transmission port closed :(
Ohhh okay, this is what I got.blacke4dawn wrote:That looks to be a full comprehensive scan of the first 1056 ports, not enough to actually reach the ports Transmission uses.
On the page with the "GRC's instant UPnP Exposure Test" button you will have a input box slightly below it, enter the peer-port (51413 by default) there and then press "User Specified Custom Port Probe". That should do it.
Looking over your OP again makes question if this is needed at all. Not sure if it's been fixed now but Transmission's own routine to check if the port is open or not hasn't been that reliable.
----------------------------------------------------------------------
GRC Port Authority Report created on UTC: 2013-07-07 at 14:27:14
Results from probe of port: 51413
0 Ports Open
0 Ports Closed
1 Ports Stealth
---------------------
1 Ports Tested
THE PORT tested was found to be: STEALTH.
TruStealth: FAILED - ALL tested ports were STEALTH,
- NO unsolicited packets were received,
- A PING REPLY (ICMP Echo) WAS RECEIVED.
----------------------------------------------------------------------
Re: Transmission port closed :(
How do you do that? I'm so sorry for the trouble, and thanks a ton for your help!x190 wrote:So now you need to check for ISP blocking or firewalls, including the one in your router.