standard problem - probably - with Port Forwarding

[dirk42799]

Hi everybody,

what can I tell: I am trying HFS and it won´t work properly.

HFS, running on Port 81, says everything´s alright (when doing the self test).
In my Netgear router I have installed a service with port 81 and a firewall setting (within the router) forwarding the service to my local IP 192.168.0.2.

But when I try to access the shared folder via my dynDNS-account I am directed to the router-log-in.

Could anyone pls help me?

Dirk

[MarkV]

If you are still inside your LAN, you can't use the DynDNS. The external IP will only work if you are outside.

Inside the LAN, use the internal IP or the name of the server PC.

If the test is successful, you are good to go - however, for any port other than 80, you need to include it in the URL, like http://mydomain.tld:81 .

[dirk42799]

Hi Mark

and thanx for answering.
It feels strange to discuss with a German in English.

Anyway:
what do you mean with adding the port to the address?
Is it the xxx.dyndnx.org-address or the address I am forwarding to?

Dirk

[bacter]

you must use http://adress:portnumber tu access your server.

from internet, your address is xxx.dyndns.org, and you use port 81. So the full url you must use is: xxx.dyndns.org:81

inside your lan you must use: 192.168.0.2:81 or localhost:81 on your pc.

if you do not specify the portnumber (81), port 80 is assumed by default.

[MarkV]

Exactly. The only port that can be omitted is 80 - every other must be specified.

[dirk42799]

Hello

and thanks.

In the meantime I´ve tried another Router (Netgear DB834PNB), checked on the port forwarding rules and finally also realised:
from within the LAN I cannot access the server software.

But an external test showed that my server is up and running.

Thanks to you!

Bye,

Dirk

[MarkV]

Inside the LAN use the local IP. This is a NAT limitation.