Zyxel NSA310 External Network Access Setup: Configuring Dasan H660GW, TP-LINK Archer D5 & No-IP

I give up - I have no chance to grasp it myself.
I've had the Zyxel NSA310 for a week. As long as everything works fine in the local network. I can't get to him from "The World".
Configuration.
Dasan H660GW - this is the main WIFI network, but coverage is not everywhere. After the previous "Internet" I was left with a TP-LINK router - Archer D5 and it is connected to Dasana. Zyxel is connected to TP-LINK. With this TP-LINK, WIFI coverage is much better and basically reaches the entire home - so there is no problem with access to Zyxel. If necessary, I unplug the cable and connect it to Dasana. I have a registered domain on No-Ip, but when I enter all the data in Zyxel, I see an internal and external address, but I can't get to this server from another network. After reading a lot of threads, I was troubled by port forwarding - but I have no clue about it. When buying, I thought that at this price it was equipment for laymen - maybe not super efficient, but easy to use. What and which router do I have to do so that I can get to this server from the external network? Thanks for any info.

What internet provider?
Have you set up no-ip service on your router?

Ad.1 Supplier - local cable network.
Ad.2 I did different combinations - the same in the router and the same in Zyxel, different in the router, different in Zyxel - no effects. When I enter all the data in the router - I get that the connection was successful. I can only do it in this TP-LINK, because this Dasan has a very poor configuration menu.
Link

1. Check if you have public or private IP address and required ports unblocked.
2. After checking point 1, configure no-ip on main router and Zyxel.

From what I used to do, you need to not redirect the ports but make them available
It will also be a good option for you to have DHCP turned off (dynamic IP address assignment in the local network, but only on the router where you have a NAS connected (whether via cable or Wi-Fi.
And to start, it's better to turn off DHCP and then to open ports, and maybe the router itself has "rigid profiles" FTP somewhere

Przemek52o wrote:

you try not to redirect ports but make them available

Since when have ports been made available?

sosarek wrote:

Since when have ports been made available?

I'm sorry I was wrong if I should have taken it in the Wonders of Words
I meant to unblock the ports on the router and redirect them

Pts. 2 - done - Connection Status: Success
Pts. 1 - maybe the link from the previous post will tell you something about IP addresses. when it comes to ports - I don't know which to be unblocked - everywhere they write about 80, or 8080, or 8081. Previously, in the Forwarding tab for the Zyxel address in the local network (assigned to MAC), I made the above-mentioned ports available in various configurations - ie for TCP, UDP - protocol. I have no problem what to set in Common Service Port.
PS We are talking about changes in TP-LINK all the time? - I don't know if it's important, but he's kind of second in line - he's behind this Dasan.

It depends on you which router you configure for the NAS server
Here you have a link on how to redirect ports
insert the appropriate end of NAS's ip address
sosarek if I made a mistake like "port sharing" please correct my statement

It doesn't change anything. Tomorrow I will try to deal with the second router.

@kadzislaw
What IP - private or public?

And you realize that if you want to connect with it from the outside, you need a lot of UPLOAD - what is it now?

Link
Dowload cuts my card - not overwhelming. But I think the upload is ok.
IP - internal Zyxel - 192.168.1.101 - assigned to MAC
IP - external 5.134.79.109 - i.e. probably public

I guess you just can't with this hardware configuration.
I do not know if this will help, but tomorrow I am going to get a fixed IP from the operator. I have made ports available on each router according to the instructions and it does not work - still no access from the outside.
The only thing that worked (accidentally) is that I don't have to unplug the cable - I have access regardless of which local network I am connected to.

Welcome.
I stick to the post. I have recently owned a Zyxel 310 NAS and while in LAN it works fine, I mainly store company-related files on it and I want to share it also to have access to it anywhere. I want to map the drives so that you don't have to log in somewhere there every time.
The NAS is plugged into the UPC router, which automatically communicated with the server itself and assigned the appropriate ports for it. I set it up with No-ip and it points me to an external IP but I can't connect to it via this number or domain in any way. if someone can help me, give me some tips, I will be grateful

kgreszczuk wrote:

I want to map the drives so that you don't have to log in somewhere there every time.

kgreszczuk wrote:

I set it up with No-ip and it points me to an external IP but I can't connect to it via this number or domain in any way.

We map the disks in the local network neighborhood.
If you want to retrieve a disk from the LAN from the domain, the UPC modemorouter must support NAT Loopback, and you will not do this on any current UPC modemorouter because it does not have such a function.

Thanks for the answer. This NAT Loopback is IP redirect, correct?
If I connect a router with such a function to that with UPC, will it talk?
Second question, can I start FTP without such a router and connect to it via TC or filezille?

kgreszczuk wrote:

If I connect a router with such a function to that with UPC, will it talk?

Specify where you want to map this drive - in the LAN or via the Internet?
If in LAN you map it as a drive mapping in network neighborhood. And if you want to share the disk via the Internet, NAT Loopback is not needed for anything, because you log in to the server's IP or its domain.

kgreszczuk wrote:

Second question, can I start FTP without such a router and connect to it via TC or filezille?

Yes, but then the NAS must be connected directly to the computer and then you will be able to use it only on one computer (where you plug the new NAS).

This is exactly what I mean to access the NAS via the Internet.

This is how I felt ...
The server itself must be properly configured for external access.
I don't know if Zyxel doesn't have its own factory domain like Synology / Qnap.
What's more, a strong UPLOAD is also necessary here.
If you have less than 20Mb on uploading to the Internet, it will be a pain.

KOCUREK1970 wrote:

This is how I felt ...
The server itself must be properly configured for external access.
I don't know if Zyxel doesn't have its own factory domain like Synology / Qnap.
What's more, a strong UPLOAD is also necessary here.
If you have less than 20Mb on uploading to the Internet, it will be a pain.

Fortunately, I have a good upload. The domain given in my zyxel310 is something that is not in Polish and by entering the data it does not search for this model anymore. Maybe too old and I have to figure it out differently.
I have a few more questions for you but I would prefer it privately and there is no forum.

kgreszczuk wrote:

Just the domain given in my zyxel310 is some kind not in Polish and by entering the data, it does not look for this model anymore

And what internet are you trying to call up Zyxel's IP address or domain name?

I wrote to you at PW.