This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Hello people.Recently i bought an rn102 with 3tb red disk ,.
I did install all fine , i am able streaming my movies/series to my smart tv though that happens only in my home.
When i am out and wanna see something can't see anything because it doesn't load
I made no ip account , setup up it in my tp link modem cause it got that option for dynamic dns , then added ddclient to my nas and configured the ddclient.conf manually with terminal from my mac.
No ip account got my main pc ipv4 address.
So , i want to know what from this went wrong.What i have to change to my nas or either to my modem so it will be fully working.
Thanks in advance.
Ps: I have read lot of articles without fixing it , thats why i opened a new topic.
You shouldn't be using port 80. The admin panel uses https, not http. That usually uses port 443. Port 80 won't work unless you enable http admin access in the NAS (which you SHOULDN'T).
So you could forward 443.
But If you have other devices that you might want to access remotely (including your router's admin page) you can pick a different port to forward. For example 54321. You'd configure 54321 as the secondary https port in system->services. Forward 54321 in the router. And access the admin page as https://vkoukoutis.ddns.net:54321/admin
Well , i want to be able to use my files outside home from my iPhone Application & an another computer so i can use my Transimission / Plex and generally my whole Nas functionality.
You will need to forward the plex port in your router to the NAS. That involves reserving an IP address for the NAS in the router, and forwarding the port to the IP address. The default port that Plex uses is 32400 - but you can change that in the plex ui if you wish.
ReadyCloud is a convenient way to access your files remotely, but there are other ways to access your NAS remotely, you can ask about them here if you find ReadyCloud doesn't meet your needs.
About Plex so I must open my 32400 port to my modem so I can access it like vkoukoutis.ddns.net:32400/web wherever I am right ? Also I want remotely access my admin panel and transmission panel the same way Ex vkoukoutis.ddns.net:8181 like that for transmission
@vkoukoutis wrote: Well thank first of all for your replies
About Plex so I must open my 32400 port to my modem so I can access it like vkoukoutis.ddns.net:32400/web wherever I am right ?
32400 is the default port, and you generally do need to forward it. Though the app connects to the plex cloud. plex.tv/web will find it, you don't need to use your ddns address to connect.
Also I want remotely access my admin panel and transmission panel the same way Ex vkoukoutis.ddns.net:8181 like that for transmission
Any possible way to do that ?
Yes. You forward the ports in your router to the NAS, and check that they are actually open (not blocked by your ISP) with http://www.canyouseeme.org/ or a similar port checker.
For https I suggest configuring a secondary https port in the NAS (something between 49152-65535) and forwarding that.
So I must go to https in system settings and add a second port then forward it to my modem right ? Then noip will work fine I guess But what happens when my Nas ip changes for example from 192.168.1.101 to 192.168.1.100 ? At port foward as ip I use Nas ip 192.268... Or my modems one 192.167.1.1 ? This is the part I have got confused
Sorry for double post About the ports I did it but only think I can access is my Plex not transmission And if my Nas ip change I also have to change it in my port foward
About the ports I did it but only think I can access is my Plex not transmission And if my Nas ip change I also have to change it in my port foward
If you can access transmission locally in your browser, there almost probably is a way to forward the port. If it has to be 8181, you can still forward port xxxx to port 8181 in the router. If the web app is mis-designed you might have a problem (sometimes controls and images hard-code the port in the html). But that usually isn't the case.
As far as IP address changes - almost all routers have a way to reserve the IP address that is assigned. On newer netgear routers that feature is called "address reservation". The name is sometimes confusing in other routers - if you can't figure that out, post the router model here. A link to the user manual for the router would also be helpful (I'm far more likely to respond if I don't have to scour the internet for the manual).
Of course any forwarding does expose the NAS to the internet, so you want to be selective about what you forwarding.
I am having to link archer d2 modem router so I want to know the configurations I got to do I just need it for remote admin panel,Plex and also upload torrent while I am not home There you go for the manual http://www.tp-link.com/res/down/doc/Archer_D2(UN_V1_UG.pdf
Look at section 6.3 of your manual (IP & MAC Binding) to reserve an IP address. The manual is focused on ARP attacks, but the procedure also locks in the IP address for the NAS (or any other MAC address you assign). The MAC address for the NAS is shown on the network page of the web ui. Your router also shows it (as noted on page 27). It's quickest to bind the MAC address to the current IP address assigned to the NAS. If you don't do that, you will need to reboot the router for it to take effect.
Section 11.1 tells you how to forward ports. The manual is a bit sketchy, but usually you can define your own names for each service (e.g., plex, or transmission). Port triggering won't work for this.
Reserve IP address for Nas means even if it restarts modem or Nas my ip will be still the same like 192.168.1.101 right ? About virtual servers yes I already got that
I am a bit confused about Nas ip and how it can be static even if both modem and Nas restarts
I am a bit confused about Nas ip and how it can be static even if both modem and Nas restarts
When the NAS requests an IP address, it includes its MAC address in the request. That is standard behaviour for dhcp/automatic address assignment. The router checks its binding list, and when it finds the MAC address there, it simply assigns the IP address it finds in the binding table. Also, it won't assign a bound address to any other device. The MAC address is hard-wired into the ethernet (or wifi chip) in the device, so it doesn't change.
You could alternatively configure a static address in the NAS. However, I don't recommend that. If you configure the static address in the NAS, you can lose the ability to access it altogether when you upgrade your router. There are ways to fix that, but it is easily avoided by using the binding feature in your router. If you were to upgrade your router, you'd lose the binding, but the NAS would still be reachable. So all you'd need to do is reassign it in the new router when you do the port forwarding. So the reserved address/binding approach is better.
If you are interested in learning more about how networking works, understanding more about how MAC addresses are used is a useful topic to research.
You shouldn't be using port 80. The admin panel uses https, not http. That usually uses port 443. Port 80 won't work unless you enable http admin access in the NAS (which you SHOULDN'T).
So you could forward 443.
But If you have other devices that you might want to access remotely (including your router's admin page) you can pick a different port to forward. For example 54321. You'd configure 54321 as the secondary https port in system->services. Forward 54321 in the router. And access the admin page as https://vkoukoutis.ddns.net:54321/admin
I saw that at address reservation also needs to bind MAC address and ip Then bind to my security section as you mentioned at 6.3 before Is that correct ?
