nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Child Item

Accessing NAS Remotely

cianr

Hi all,

Id really appreciate some help - Ive spent the last 3 hours Googling this with no luck! I'm trying to connect to my NAS remotely - it seems (I think) that my router's ports are not open correctly. Here is the setup:

Router 192.168.1.1 (Vodafone branded Huawei HG556a)
NAS 192.168.1.32 (Zyxel NSA325 with a static IP)

At home if I type the IP of the NAS it opens the config page for that (I can also telnet into the NAS from my PC on my home network) - however if I type my external IP into my browsers it loads the config page of my router.

On the router I have forwarded lots of ports that I have found mentioned in various articles - e.g. Source Port 8080 / Destination IP 192.168.1.32 / Destination Port 8080. However if I check online (http://www.yougetsignal.com/tools/open-ports/) it says that port 8080 is closed. On the router I have also added the NAS's IP to the DMZ (I've tried it with and without the DMZ entry - Ive also tried turning on/off uPnp on the router). Ive also rebooted the router but no luck.

Really appreciate any help! Thanks!!

Find more posts tagged with

Quick Links

Comments

whizbang

Thats pretty normal behaviour for some routers. it (and/or you) doesnt understand your route. why go to the internet for a local address?
you must use an external network. Also, how are you getting your IP for you to connect remotely ?

28064212

Should the port not be 80?

CreepingDeath

28064212 wrote: »

Should the port not be 80?

Good point.
Although I'd hope for security they're using HTTPS which is port 443.

Also, I'd try avoiding exposing known ports to the internet like that.
You should be able to configure "port forwarding" on your router to solve this.

1. Define a static ip address for your NSA325, so it doesn't change in your local lan.

2. Configure port forwarding on your router to map some arbitrary port say 29999 to your local IP and port 443.

Then outside your lan, you should be able to access your secure page with

https://<your public wan ip>:29999

28064212

CreepingDeath wrote: »

Good point.
Although I'd hope for security they're using HTTPS which is port 443.

It's not on by default, but you can turn it on in "Maintenance - SSL"

CreepingDeath wrote: »

Also, I'd try avoiding exposing known ports to the internet like that.
You should be able to configure "port forwarding" on your router to solve this.

1. Define a static ip address for your NSA325, so it doesn't change in your local lan.

2. Configure port forwarding on your router to map some arbitrary port say 29999 to your local IP and port 443.

Then outside your lan, you should be able to access your secure page with

https://<your public wan ip>:29999

Unfortunately, a lot of routers (like mine) don't allow you to map different ports. The NSA325 has an option for specifying a different HTTP configuration port ("Network - TCP/IP - HTTP (Web Configurator)"), but it doesn't appear to work with the SSL option above. So if your router doesn't support different ports, you can either have SSL OR a different port