I don't remember the password

[matpic]

Usually, you only have to do in one place. Your router or DDNS feature of the firmware do both the same thing: to allow the provider to update your public IP with your DDNS . So do it twice is not helpful.

Note: If you keep the firmware feature, the settings for FTP for remote access, HTTPS and WebDAV server will be a little easier because the firmware then knows your DDNS.

Ok I keep only the firmware feature activated.I think I also have port 9091 open. is it normal that if I digit myhostname.dyndns.org:9091 from my pc (not a remote one) it tells me "impossible to connect to the page" ? do I have to just go from a remote pc?

[Jocko]

I assume that you opened the port 9091 on the router.
but also some router don't like this lookup calls itself...

Note : I tested with my ddns if I open the port 9091 (TCP protocol toward my NAS IP LAN). I can access to transmissioncli GUI

[matpic]

I assume that you opened the port 9091 on the router.
but also some router don't like this lookup calls itself...

Note : I tested with my ddns if I open the port 9091 (TCP protocol toward my NAS IP LAN). I can access to transmissioncli GUI

in the router do I have to select inbound service or outbound?

[Jocko]

Haha !...
I forgot that with your netgear you must set also the firewall (many ISP routers do it automatically)

So after creating the port forwarding, you must set a rule in the inbound service to 'allow always' send to your NAS LAN IP from 'any' (but you can also set a WAN IP range for safety if you know what IP will try to connect)

[matpic]

Haha !...
I forgot that with your netgear you must set also the firewall (many ISP routers do it automatically)

So after creating the port forwarding, you must set a rule in the inbound service to 'allow always' send to your NAS LAN IP from 'any' (but you can also set a WAN IP range for safety if you know what IP will try to connect)

this is the situation on my router:
http://tinypic.com/r/33tj9mw/5
http://tinypic.com/r/hx0ocl/5

still no luck when I try to enter matpic.dyndns.org:9091

[Jocko]

Humm :scratch

I see that you enable the log over this rule. So try to read the log content.

You can check if the port 9091 is really opened by using this url http://www.yougetsignal.com/tools/open-ports/. It must return yes

If not, there is an issue with the router. Usually, the router allows any out packets but maybe not with your router so you should create also a rule in the outbound

[matpic]

Humm :scratch

I see that you enable the log over this rule. So try to read the log content.

You can check if the port 9091 is really opened by using this url http://www.yougetsignal.com/tools/open-ports/. It must return yes

If not, there is an issue with the router. Usually, the router allows any out packets but maybe not with your router so you should create also a rule in the outbound

I tested and yes port 9091 is open
I can see transmission interface if trying 192.168.0.13:9091 but not if using matpic.dyndns.org:9091 so maybe is something wrong withe the dyndns thing?

[Jocko]

Hi matpic,

Yes it seems that there is something wrong with your ddns.

So you must check if it's ok :
What is the DDNS status in the LAN setup menu. You must get these information

Code: Select all

DDNS Status   Sat 21 September 2013 12:57:18, yourwanIP

If not, check if you gave the right login and password of your dyndns account.

[matpic]

Hi matpic,

Yes it seems that there is something wrong with your ddns.

So you must check if it's ok :
What is the DDNS status in the LAN setup menu. You must get these information

Code: Select all

DDNS Status   Sat 21 September 2013 12:57:18, yourwanIP

If not, check if you gave the right login and password of your dyndns account.

yes in the ddns status I get the correct information you are reporting

[Jocko]

:scratch

What service did you set with your DDNS?
You must chose "Host with IP address" in this url https://account.dyn.com/dns/dyndns/matpic.dyndns.org (of course use it only after signing...)