• February 24, 2025, 02:38:03 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: transmission incoming port on your daemon is closed  (Read 16622 times)

stanchiam

  • Level 1 Member
  • *
  • Posts: 20
transmission incoming port on your daemon is closed
« on: August 19, 2010, 05:23:42 AM »

Hi,

I install transmission on dns323 but noticed that downloading is extremely slow
When i check with transmission remote, i get
The incoming port on your daemon is closed

How can i open it?

Logged

gunrunnerjohn

  • Level 11 Member
  • *
  • Posts: 2717
Re: transmission incoming port on your daemon is closed
« Reply #1 on: August 19, 2010, 05:25:31 AM »

Assign the DNS-323 a static IP address on your network and open the port in your router to the DNS_323 IP address.
Logged
Microsoft MVP - Windows Desktop Experience
Remember: Data you don't have two copies of is data you don't care about!
PS: RAID of any level is NOT a second copy.

dosborne

  • Level 5 Member
  • *****
  • Posts: 598
Re: transmission incoming port on your daemon is closed
« Reply #2 on: August 19, 2010, 07:19:11 AM »

If you have UPNP enabled on your router, then it will open the port automatically.

In the transmission config file enable port forwarding
"port-forwarding-enabled": true,
(You already have this enabled per the screen shot - just mentining it for others)

You may have to restart transmission to re-enable the port if you rebooted your router after starting transmission.

The transmission log should show something like this upon success
[06:53:29.944] Port Forwarding (NAT-PMP) initnatpmp succeeded (0) (natpmp.c:67)
[06:53:29.945] Port Forwarding (NAT-PMP) sendpublicaddressrequest succeeded (2) (natpmp.c:67)
[06:53:30.953] Port Forwarding (UPnP) Found Internet Gateway Device "http://192.168.1.1:2869/upnp/control/WANIPConn1" (upnp.c:113)
[06:53:30.954] Port Forwarding (UPnP) Local Address is "192.168.1.41" (upnp.c:115)
[06:53:32.965] Port Forwarding (UPnP) Port forwarding through "http://192.168.1.1:2869/upnp/control/WANIPConn1", service "urn:schemas-upnp-org:service:WANIPConnection:1".  (local address: 192.168.1.41:57500) (upnp.c:202)
[06:53:32.966] Port Forwarding (UPnP) Port forwarding successful! (upnp.c:205)
[06:53:32.966] Port Forwarding Forwarded (port-forwarding.c:89)


If you have random ports enabled, you may want to switch to a single static port and manually forward it as gunrunnerjohn suggests.
« Last Edit: August 19, 2010, 07:40:21 AM by dosborne »
Logged
3 x DNS-323 with 2 x 2TB WD Drives each for a total of 12 TB Storage and Backup. Running DLink Firmware v1.08 and Fonz Fun Plug (FFP) v0.5 for improved software support.

stanchiam

  • Level 1 Member
  • *
  • Posts: 20
Re: transmission incoming port on your daemon is closed
« Reply #3 on: August 19, 2010, 09:34:56 AM »

ok, i have done that
but still receiving the same error message when doing test port


and my router i can see the forwarded port 52888 for the dns ip 192.168.1.112
so port forwarding is no problem, how to check for the problem?
any command to use in telnet?
Logged

scaramanga

  • Level 2 Member
  • **
  • Posts: 99
Re: transmission incoming port on your daemon is closed
« Reply #4 on: August 19, 2010, 11:33:58 AM »

Forward both TCP and UDP.
Logged
DNS-323 HW Rev. C1 FW 1.08 fun_plug 0.5
2 x Western Digital WD10EARS-00Y5B1 in Standard mode
(LLC changed to 5 minutes. Partitions aligned to 4K boundary)

stanchiam

  • Level 1 Member
  • *
  • Posts: 20
Re: transmission incoming port on your daemon is closed
« Reply #5 on: August 19, 2010, 05:49:04 PM »

yes, i have manually forwarded both in router but still the same.
My first installation of transmission cannot work and i reinstall again, this time it work but i have this strange problem.
Logged

irotjaf

  • Level 2 Member
  • **
  • Posts: 51
Re: transmission incoming port on your daemon is closed
« Reply #6 on: August 19, 2010, 06:58:24 PM »

There is a mismatch. On the figure of transmission setting you have 63080. But you said you froward port 52888. Are you using the right port? Try to forward 63080 and go to canyouseeme.org to check when you succeed with forwarding.
Logged

scaramanga

  • Level 2 Member
  • **
  • Posts: 99
Re: transmission incoming port on your daemon is closed
« Reply #7 on: August 20, 2010, 02:15:04 AM »

There is a mismatch. On the figure of transmission setting you have 63080. But you said you froward port 52888. Are you using the right port? Try to forward 63080 and go to canyouseeme.org to check when you succeed with forwarding.
That 63080 port is the port number Transmission Remote communicates with the Transmission Daemon (RPC/Web port).
You can find the server port for torrenting in the screenshot: "peer-port" and "peer-port-random-on-start".
I have to say your setup looks OK.

In Tomato: Did you hit save after you changed the settings? Do you have UPnP enabled?
In Transmission: Did you check Transmission log (/mnt/HD_a2/.transmission-daemon/transmission-daemon.log)?
Logged
DNS-323 HW Rev. C1 FW 1.08 fun_plug 0.5
2 x Western Digital WD10EARS-00Y5B1 in Standard mode
(LLC changed to 5 minutes. Partitions aligned to 4K boundary)

dosborne

  • Level 5 Member
  • *****
  • Posts: 598
Re: transmission incoming port on your daemon is closed
« Reply #8 on: August 20, 2010, 06:49:26 PM »

That 63080 port is the port number Transmission Remote communicates with the Transmission Daemon (RPC/Web port).
I think you are in error. The RPC com port for the UI is under Local Settings -> Server Settings -> Server -> Port.

The incoming port for the torrent u/l d/l is the one shown in the screen capture and that is why the "Test Port" button is right next to it.

Posting the log would be the best way to clear up the issue though.
« Last Edit: August 20, 2010, 06:56:17 PM by dosborne »
Logged
3 x DNS-323 with 2 x 2TB WD Drives each for a total of 12 TB Storage and Backup. Running DLink Firmware v1.08 and Fonz Fun Plug (FFP) v0.5 for improved software support.

scaramanga

  • Level 2 Member
  • **
  • Posts: 99
Re: transmission incoming port on your daemon is closed
« Reply #9 on: August 21, 2010, 12:29:13 AM »

I think you are in error. The RPC com port for the UI is under Local Settings -> Server Settings -> Server -> Port.

The incoming port for the torrent u/l d/l is the one shown in the screen capture and that is why the "Test Port" button is right next to it.

Posting the log would be the best way to clear up the issue though.

You're right. Got mixed up. The screenshot says server port is 63080 but the settings file says "peer-port" is 52888. They should both be 52888.
Logged
DNS-323 HW Rev. C1 FW 1.08 fun_plug 0.5
2 x Western Digital WD10EARS-00Y5B1 in Standard mode
(LLC changed to 5 minutes. Partitions aligned to 4K boundary)

stanchiam

  • Level 1 Member
  • *
  • Posts: 20
Re: transmission incoming port on your daemon is closed
« Reply #10 on: August 22, 2010, 01:32:17 AM »

sorry about the screen shot, i have since change the port to 52888 and make sure all is forwarded correctly, but still the same result when i click on the "Test Port" button in the Transmission remote




the incoming port of your daemon is closed
Logged

stanchiam

  • Level 1 Member
  • *
  • Posts: 20
Re: transmission incoming port on your daemon is closed
« Reply #11 on: August 22, 2010, 02:47:50 AM »

by the way, i delete funplug and install DebNas and have successfully compile transmission-2.04
still the same error message, have started transmission-daemon -g /mnt/HD_a2/.transmission-daemon
it is running ok, only thing is i cannot find the transmission.log
not sure where it is after installing it in debian lenny
Logged

stanchiam

  • Level 1 Member
  • *
  • Posts: 20
Re: transmission incoming port on your daemon is closed
« Reply #12 on: August 22, 2010, 02:54:00 AM »

by the way, when i download the same torrent using my pc, i am able to see more than 1000 peers and download speed of about 200k
using transmission, i am only able to see about 60 peers and download speed of about 2-15k and it keep dropping to zero even few seconds.
Logged

monkeylove

  • Level 1 Member
  • *
  • Posts: 15
Re: transmission incoming port on your daemon is closed
« Reply #13 on: April 26, 2012, 03:41:35 AM »

I have the same problem, but with Transmission installed in a Buffalo NAS and connected to a DIR-655. I also installed uTorrent and Transmission for Windows in a Win 7 PC connected to the router. uPNP is turned on and port forwarding for both clients.

I'm using a cable modem, with connections automatically going through a proxy assigned by the ISP.

Transmission reports that its port is closed. When I telnet to the NAS and run

netstat -nat | grep LISTEN

it lists the port, so I'm guessing that the port is open.

uTorrent reports that its port is open.

When I go to CanYouSeeMe.org, it reports that either port is closed.

I tried static IP addresses and manual port forwarding, and the results are the same.

Speed seems to be more consistent for the uTorrent installed in the desktop. For Transmission installed in the NAS, the speed goes up and down. I'm guessing that processor and memory limitations in the NAS makes this happen.

Finally, I'm guessing that the proxy of the ISP is blocking the Transmission port checker and CanYouSeeMe but not the uTorrent port checker.
Logged