Want to add a second NAS - Need help in how to configure network AND remote access to both

[Telos]

might it be connecting the two purely based on my logged-in Plex account

Plex is a can of worms on its own. Do not use the Plex servers for your remote connections. You will see buffering and transcode issues. Plex must be connected by direct means... DDNS, VPN, and do on. For example:

plex.secret.synology.me:32400

It seems you need to sort out your remote access needs first. Start simple. Can you log into your NAS remotely... then add apps, etc., building on RP settings.

 

[Rusty]

and wouldn't be used for backup, or have backup software installed (IMO, using RAID5 is it's own "backup", as the probability of 2 drives failing at the same time is slim-to-none)

While this is a side comment and has no direct connection to the original topic of the thread, let me just say, you would be surprised how often it can happen to have the second drive fail when you didn't expect it. RAID is not backup, but redundancy. Having a separate backup would be wise.

speaking of which (quick side question), would I be better off leaving them as Dynamic, or should I sign them a Static IP?

Any "server" device should be configured with a static IP as a general rule

I'm assuming (possibly incorrectly) that, even though it's an 'external' app, since it's on the same network, I'm wondering if it also connects based on IP address,

It does. Plex will detect that the client is on the same LAN subnet and make a direct connection that way.

Starting with what might actually be the easier one, Plex, is Plex on the tablet accessing Plex on the NAS via some form of "Web services"...or, as I surmised with the TV, might it be connecting the two purely based on my logged-in Plex account? If the 'connection' is purely through the Plex account login, then might then be no changes in the NAS's settings?

Considering your needs and all that @fredbert wrote correctly in terms of RP, with Plex you might be just inclined to simply allow direct remote access on your router.

A simple Plex port (default 32400 unless changed) port forward with activating "remote access" feature inside Plex settings. This has no need of any reverse proxy settings at all, and will allow the Plex mobile app to connect to the Plex server.

Even if you have multiple Plex servers this can be done by simply forwarding each Plex instance to its own forward port. Once you log into the client app with your Plex account, you will (just like in local) see all Plex servers that you have access to.

While there is no need to proxy Plex, keep in mind that you can do that as well, but keeping things simple, this will work just as well.

Moving over to the 'data' NAS, whether being accessed through Synology Drive, or DS File, is this considered "Web services"? Put another way, is "reverse proxy" needed? Or some other "alternate configuration" needing to be done within DSM? Or, does morning actually need to be done?

Short answer (again as @fredbert explained) is yes. But, you need to understand what app you need in the first place. File Station (and mobile DS File) is your standard file manager, while Drive platform is more than that. It is a backup and sync tool with an added bonus that it allows access to selected teams folders as well (that you can choose). Look at it as a Synology Dropbox/Google Drive alternative in terms that it allows for syncing data, but also end user client data backup (as a separate function).

You can proxy those, but you can also access them via a standard DDNS name that you can configure using the "Login Portal" (inside Control Panel). Considering QC is not something you want to use, DDNS and RP will require some more attention but as you already understand why that is, there is no point in elaborating on that.

Bottom line, once you decided what app you want to use (or both) you can configure them via RP. Going down that route, you will also need to maintain SSL certificate(s) to have it all secure end to end.

 

[Panther6834]

While this is a side comment and has no direct connection to the original topic of the thread, let me just say, you would be surprised how often it can happen to have the second drive fail when you didn't expect it. RAID is not backup, but redundancy. Having a separate backup would be wise.


Any "server" device should be configured with a static IP as a general rule


It does. Plex will detect that the client is on the same LAN subnet and make a direct connection that way.


Considering your needs and all that @fredbert wrote correctly in terms of RP, with Plex you might be just inclined to simply allow direct remote access on your router.

A simple Plex port (default 32400 unless changed) port forward with activating "remote access" feature inside Plex settings. This has no need of any reverse proxy settings at all, and will allow the Plex mobile app to connect to the Plex server.

Even if you have multiple Plex servers this can be done by simply forwarding each Plex instance to its own forward port. Once you log into the client app with your Plex account, you will (just like in local) see all Plex servers that you have access to.

While there is no need to proxy Plex, keep in mind that you can do that as well, but keeping things simple, this will work just as well.


Short answer (again as @fredbert explained) is yes. But, you need to understand what app you need in the first place. File Station (and mobile DS File) is your standard file manager, while Drive platform is more than that. It is a backup and sync tool with an added bonus that it allows access to selected teams folders as well (that you can choose). Look at it as a Synology Dropbox/Google Drive alternative in terms that it allows for syncing data, but also end user client data backup (as a separate function).

You can proxy those, but you can also access them via a standard DDNS name that you can configure using the "Login Portal" (inside Control Panel). Considering QC is not something you want to use, DDNS and RP will require some more attention but as you already understand why that is, there is no point in elaborating on that.

Bottom line, once you decided what app you want to use (or both) you can configure them via RP. Going down that route, you will also need to maintain SSL certificate(s) to have it all secure end to end.

Finally, a more thorough, more informative, reply...not that the reply from @fredbert wasn't 'good' (it was)...but, your reply not only explained more of "why", you also took the time to 'expand' on the "why". As for DS File vs Synology Drive, I'm thinking Drive will be more appropriate, as I am hoping to have the 'data' NAS replace my current use of Google Drive.

As I'm understanding things, once I get the second NAS box (which will be for the Plex server), I should be able to just remove the already-configured 6TB drives from the older DS918+, slide them into the DS425+, boot it up, map the new drive to Windows, and the Plex server should, essentially, be "ready to go" for streaming to the TV, and (once I get Remote Play Pass) the tablet. If I misunderstood any part of it, please, let me know.

As for the DS918+, I'll have to put the 4TB drives back in, reconfigure it to RAID 5 (that drive set is still set up as RAID10), move the data (other than Plex data) from the DS425+ to DS918+, and finally configure the RP. It's that final part that's daunting.

With my current knowledge, I can easily accomplish everything described above...except the RP. Granted, I have yet to go through all DSM settings, to determine 'how' to set/configure RP...but, with the limited checking that I've already done (see it in one of my previous, albeit recent, posts), I'm confident, in part because the online directions I found don't match what's actually seen in the current version of DSM.

Going back to the QuickConnect (I might reconsider, depending on the answer to the question at the end of this paragraph), the biggest reason I didn't want to use QC was primarily because of Plex, as I felt adding additional 'legs' to how the data travels, it would slow things down, causing buffering...but, for the 'data' NAS, in regards to real-world time, how much slower would it be to access the NAS via QC, as opposed to via RP? Let's say I wanted to remotely move 10GB of photos from my phone, to the NAS. Or I wanted to view a 2GB video on my tablet that's stored on the NAS. Or maybe I want to move several recently-filmed videos from my phone, to the NAS, for editing at home. Is there any significantly-noticable difference (in time) between doing this via RP, and doing it via QC? I know I'd prefer not using QC...but, if setting up, configuring, and maintaining, the RP is going to be 'troublesome' (which, for me, its seeming to be), then maybe QC wouldn't be "so bad".

 

[Rusty]

I should be able to just remove the already-configured 6TB drives from the older DS918+, slide them into the DS425+

There is a new HDD policy with X25 models and 3rd-party drives. Considering that Syno is advocating for their drives, moving forward, officially, this will be the only disk supported until the compatibility list is expanded with any 3rd party models.

Saying this, a pure migration of drives from x18 to x25 will be possible, but you will have to use the volume "as is". Any changes to it will require a Synology drive from that point forward (or any of many unsupported hacks that will cost you warranty and support. Still, the drives will work, ofc, but a caveat is there).

slide them into the DS425+, boot it up, map the new drive to Windows, and the Plex server should, essentially, be "ready to go" for streaming to the TV, and (once I get Remote Play Pass) the tablet. If I misunderstood any part of it, please, let me know.

Now moving past the drive migration, yes, once you get the DSM up and running again, installing Plex on the 425, you are good to go with local access, and with external one, forwarding the Plex port and configuring it for remote access, you will open up communication via the mobile/tablet app.

With my current knowledge, I can easily accomplish everything described above...except the RP. Granted, I have yet to go through all DSM settings, to determine 'how' to set/configure RP...but, with the limited checking that I've already done (see it in one of my previous, albeit recent, posts), I'm confident, in part because the online directions I found don't match what's actually seen in the current version of DSM.

As @fredbert already pointed out, there is a "resource" section on the forum that you can search for a number of RP tutorials, including the one where RP is a part of the DSM. Regardless of those few visual changes in the UI, the main thing is that nothing major has happened under the hood, so you will be able to follow along. If you get stuck, write back or PM, and things will get sorted.

Going back to the QuickConnect (I might reconsider, depending on the answer to the question at the end of this paragraph), the biggest reason I didn't want to use QC was primarily because of Plex, as I felt adding additional 'legs' to how the data travels, it would slow things down, causing buffering...but, for the 'data' NAS, in regards to real-world time, how much slower would it be to access the NAS via QC, as opposed to via RP? Let's say I wanted to remotely move 10GB of photos from my phone, to the NAS. Or I wanted to view a 2GB video on my tablet that's stored on the NAS. Or maybe I want to move several recently-filmed videos from my phone, to the NAS, for editing at home. Is there any significantly-noticable difference (in time) between doing this via RP, and doing it via QC? I know I'd prefer not using QC...but, if setting up, configuring, and maintaining, the RP is going to be 'troublesome' (which, for me, its seeming to be), then maybe QC wouldn't be "so bad".

Personally, give QC a go and see. Would RP be faster? Yes, but we are not talking about hosting a site that 10k users per hour will visit. RP, while not difficult to maintain, will also have some elements that you are not familiar with that might give you a headache in the long run if it's not automated (SSL cert generation for example). While all things can be automated, it will take a certain learning curve to get there, some trial and error, and again, if this is personal usage within the household, it might be just easier using the QC.

On top of this, with Synology's new BeeStation devices, which work only either in local or via QC (no RP, no DDNS), the uptime and QC worldwide server distribution has increased. There might be some occasional issues with that service, sure, but for the most part it works really well.

The main benefit would be your local Internet connection. The speed of it as well as the technology behind it (DSL, fiber, mobile, Starlink, etc). So, depending on your location, your experience might vary. You mentioned you're from Sin City (I will guess that is Las Vegas), and while I am unfamiliar with network speeds and tech behind it, again, it would be best to just test it out and see if it's too slow or fast enough.

You can always set up one service over RP and see how it compares.

 

[Panther6834]

There is a new HDD policy with X25 models and 3rd-party drives. Considering that Syno is advocating for their drives, moving forward, officially, this will be the only disk supported until the compatibility list is expanded with any 3rd party models.

Saying this, a pure migration of drives from x18 to x25 will be possible, but you will have to use the volume "as is". Any changes to it will require a Synology drive from that point forward (or any of many unsupported hacks that will cost you warranty and support. Still, the drives will work, ofc, but a caveat is there).


Now moving past the drive migration, yes, once you get the DSM up and running again, installing Plex on the 425, you are good to go with local access, and with external one, forwarding the Plex port and configuring it for remote access, you will open up communication via the mobile/tablet app.


As @fredbert already pointed out, there is a "resource" section on the forum that you can search for a number of RP tutorials, including the one where RP is a part of the DSM. Regardless of those few visual changes in the UI, the main thing is that nothing major has happened under the hood, so you will be able to follow along. If you get stuck, write back or PM, and things will get sorted.


Personally, give QC a go and see. Would RP be faster? Yes, but we are not talking about hosting a site that 10k users per hour will visit. RP, while not difficult to maintain, will also have some elements that you are not familiar with that might give you a headache in the long run if it's not automated (SSL cert generation for example). While all things can be automated, it will take a certain learning curve to get there, some trial and error, and again, if this is personal usage within the household, it might be just easier using the QC.

On top of this, with Synology's new BeeStation devices, which work only either in local or via QC (no RP, no DDNS), the uptime and QC worldwide server distribution has increased. There might be some occasional issues with that service, sure, but for the most part it works really well.

The main benefit would be your local Internet connection. The speed of it as well as the technology behind it (DSL, fiber, mobile, Starlink, etc). So, depending on your location, your experience might vary. You mentioned you're from Sin City (I will guess that is Las Vegas), and while I am unfamiliar with network speeds and tech behind it, again, it would be best to just test it out and see if it's too slow or fast enough.

You can always set up one service over RP and see how it compares.

First, I checked out Synology Drive...and, I stand corrected...DS File, for me, is the "better" solution. While the 'sync' function is good to have, that has nothing to do with what I want/need it for. I specifically want it for moving/accessing files between the NAS, and other computers/mobile devices. For Google Drive, I do use it for syncing certain folders on my desktop & laptop...but, I do not use any sync for my phone or tablet.

Getting to your reply, first, in regards to migrating the drives, from DS918+ to DS425+, I'm not entirely certain I understand what you mean by "but you will have to use the volume "as is"". I am aware that, for example, if I started with a number of drives less that the NAS box can hold, any additional drives would have to be on the 'Compatibility List'. The same holds true if I decided to increase capacity (ie. replace any of the 6TB WD Red Plus drives with 8TB or larger). If it's only the two points I covered, I'm already aware of that, as those points have already been explained to my by Synology Support...but, beyond that, in regards to "as is", is there anything else you are referring to? If not, no worries...but, if you're inferring something beyond those two points, please, explain. As for 'installing' Plex, it's already installed, and I am already in the process of ripping movies (to one of the desktop's internal drives), and moving the files to the NAS's PlexMediaServer folder.

Regarding the Reverse Proxy information, I have already searched the forum...and, unfortunately, I was not able to find any threads dealing with my configuration situation. I found several dealing with such things as using the second NAS for backing up the first; a couple dealing with having both for normal data (meaning, no media server), but one accessable only ocally, and the other accessable locally & remotely; and one dealing with having one NAS for 'personal', and the second for 'business', but both being units purely for normal data...but, I couldn't find any dealing with one being a media server for local & remote access, and the other being for normal data for local & remote access. Plus, I didn't notice any providing actual configuration data, just "general" information, which didn't do me any good. I guess, a better way of putting it is, when someone is telling others "the type of data" to be entered, and "where to put that info", but without providing the actual data, or at least examples of the actual data, it doesn't do me any good. For those having at least some familiarity with configuring data for the NAS, I'm sure they would know, or at least be able to figure out, what specific data is needing to be entered for their needs...but, when soneone like myself comes along, and doesn't have the slightest clue (again, I'm a 'hardware' person, not a 'software' person...and, yes, I'm very well-aware of the old "lighbulb" joke ), finding "general" and/or very basic information doesn't realy do me any good.

That's why I'm on the verge of just giving up on the RP idea (I still haven't been able to find anything within the DSM's Control Panel specifically related to "reverse proxy". Heck, I still can't figure out how to set a Static IP for the NAS. I thought I had it...but, after creating a Static IP (or thinking I created it), it was still listed as "Disabled". Worse, after clicking 'Apply', and it taking aprox 30 seconds, I got a "Save failed" message...yet, I also lost my connection to the NAS. I am trying to reconnect, via Synology Assistant, and, while it 'sees' the NAS, it can't seem to connect. The 'Status' is showing "Connection failed / Ready" in red letters.

NOW, what do I do??? Obviously, I can reset the NAS connection settings (by the botton on the backside of the NAS), but there should be another way to fix this.

EDIT: I recovered acces to the NAS. Plus, I had to search for "proper" way to assign Static IP. Seems, instead of setting the Static IP via Control Panel > Network > Network Interface, I had set it via Control Panel > Network > Static Route. When I saw the word "Static", I figured that was where the change was supposed to be made. If that doesn't show how much I don't understand NAS config settings, I don't know what would.

 

[fredbert]

EDIT: I recovered acces to the NAS. Plus, I had to search for "proper" way to assign Static IP. Seems, instead of setting the Static IP via Control Panel > Network > Network Interface, I had set it via Control Panel > Network > Static Route. When I saw the word "Static", I figured that was where the change was supposed to be made. If that doesn't show how much I don't understand NAS config settings, I don't know what would.

I guess we say 'static IP' when really it is set one of two ways:

1. Manually configure the network settings. Choosing an IP address the LAN's DHCP service won't give to another device.
2. In the LAN's DHCP service reserve an IP address for the NAS's MAC address of the LAN port you use. Then use dynamic network configuration in the NAS.

Option 1 might still require you to reserve the IP address in the DHCP service, to stop it giving that address out.

So here static means it doesn't change. But the Static Route is very much different, it is a set of extra rules to tell the NAS where packets destined for certain IP subnets are are to be sent (the next hop routers for those subnets). You use Static Routes when these packets aren't to be sent to the default gateway (e.g. you router/firewall).

You assign manual IP addresses so that you will always know the IP address. Which is needed when creating port forwarding and firewall rules on the firewall/router.

 

[Panther6834]

I'm

I guess we say 'static IP' when really it is set one of two ways:

1. Manually configure the network settings. Choosing an IP address the LAN's DHCP service won't give to another device.
2. In the LAN's DHCP service reserve an IP address for the NAS's MAC address of the LAN port you use. Then use dynamic network configuration in the NAS.

Option 1 might still require you to reserve the IP address in the DHCP service, to stop it giving that address out.

So here static means it doesn't change. But the Static Route is very much different, it is a set of extra rules to tell the NAS where packets destined for certain IP subnets are are to be sent (the next hop routers for those subnets). You use Static Routes when these packets aren't to be sent to the default gateway (e.g. you router/firewall).

You assign manual IP addresses so that you will always know the IP address. Which is needed when creating port forwarding and firewall rules on the firewall/router.

I'm familiar with Static IP. I've set it up before on other devices. It's just that I didn't (initially) know how to set it up within the Synology NAS. In seeing "Static Route", all my brain really 'saw' was "Static". The fingers were already working before the brain could say, "Are you sure you wanna do that?". Next thing I knew, I was looking at a black screen on my browser, and my brain said, "I have a bad feeling about this." Thankfully, correcting the problem turned out to be easier than causing it.

Quickly going back to the origins of this thread, I was getting so discouraged in regards to gathering info for running two NAS boxes, that I was ready to give up, and just get the DX517 expansion box. Having already discussed the possibility, I knew I could set drives in the DS918+ as one RAID for 'data', and drives in the DX517 as a separate RAID for Plex. However, what Dustin (the support agent at Synology that's been replying to me) forgot, or didn't bother, to mention is that it's a SATA cable that connects the two, thus it's only Half-Duplex. Why didn't Synology design these boxes to use SAS cables (ie. Full-Duplex)? One step forward, one step back...ugh.

 

[Rusty]

If it's only the two points I covered, I'm already aware of that, as those points have already been explained to my by Synology Support...but, beyond that, in regards to "as is", is there anything else you are referring to?

I was refering that the new 2025 NAS models (x25) are presently only (officially) compatible with Synology branded disks. Migrating non-supported drives will work, as long as the volume stays as it is now. Any further changes to it, like replacing a drive, expanding the volume, or starting a fresh volume will require Synology drives. Ofc you can use alternate methods to adopt 3rd party drives with the x25 series but you will lose any support and void the warranty from Synology perspective.

Be

Why didn't Synology design these boxes to use SAS cables (ie. Full-Duplex)?

Because the x18 models are now 6y old and Syno was never one for latests and greatest. The x25 models are running with USBC and the RS models are using SAS connectors. It depends on the tier of their products tbh.

While we are on the expansion vs 2nd nas topic, do consider going with 2 NAS units over the expansion. You will pay almost the same amount for the expansion as a separate NAS unit and you will still be dependent on the main NAS in that case. eSATA a side, and the fact that you can have two separate volumes ofc, you will have more flexibility with two separate NAS units that with NAS+exp setup for sure.

 

[Telos]

I had to search for "proper" way to assign Static IP. Seems, instead of setting the Static IP via Control Panel > Network > Network Interface,

This is less than ideal (and certainly not “proper”). Instead, leave this at DHCP default, and set “reserved” IPs for your devices through your router.

 

[Panther6834]

This is less than ideal (and certainly not “proper”). Instead, leave this at DHCP default, and set “reserved” IPs for your devices through your router.

You forget (or never knew) that NOT all routers have that ability. Plus, setting a Static IP has always been done from the device, not the router. I've been building computers for approx 30 years, and I've always set the Static IP from the device. My dad, who worked from an IBM subsidiary for almost 40 years, did the same. So, are you going to say that IBM's been doing it wrong this whole time?

 

[Panther6834]

Because the x18 models are now 6y old and Syno was never one for latests and greatest. The x25 models are running with USBC and the RS models are using SAS connectors. It depends on the tier of their products tbh.

While we are on the expansion vs 2nd nas topic, do consider going with 2 NAS units over the expansion. You will pay almost the same amount for the expansion as a separate NAS unit and you will still be dependent on the main NAS in that case. eSATA a side, and the fact that you can have two separate volumes ofc, you will have more flexibility with two separate NAS units that with NAS+exp setup for sure.

On the newer models using SAS, understood. And, on using 2 NAS, as opposed to 1 NAS & 1 expansion, agreed.

 

[fredbert]

You forget (or never knew) that NOT all routers have that ability. Plus, setting a Static IP has always been done from the device, not the router. I've been building computers for approx 30 years, and I've always set the Static IP from the device. My dad, who worked from an IBM subsidiary for almost 40 years, did the same. So, are you going to say that IBM's been doing it wrong this whole time?

I do both. Set the IP address and other network parameters manually, but also reserve the IP address in the DHCP service. That's because I have the full subnet range in DHCP rather than restricting DHCP to a sub-range. If I were still using a sub-range in DHCP I wouldn't have to do a reservation.

While it's true that DHCP service is not a mandatory feature on a router, many (or all that I've seen in 25 years) home routers do have a DHCP service. It can equally be said that firewalls aren't mandatory feature of routers, but home routers have them to a greater or lesser degree.

Most businesses will run separate DHCP, DNS, and perimeter security services but most people here aren't in that category.

From what's been said so far it seemed a reasonable assumption that you'd have a router/firewall with a DHCP service. It seemed an honest assumption.

 

[Telos]

setting a Static IP has always been done from the device

Old ways die hard. Setting a fixed IP on the device does not prevent the router from giving that IP to another device, unless your router permits you (and you have made the effort to) restrict the router's DHCP range.

Additionally, when your change routers, or ISPs, and use an ISP router, you're likely to find yourself unable to connect to devices which were IP locked. For the NAS, this often mean a reset.

Reserving IPs within the router is convenient. In that manner, the IPs of all devices are centrally managed by the device that hands out IPs (obvious, huh?), and not scattered among the various devices (of which the administrator may not have ready access). Additionally, regular router settings backups help ensure the IP settings are preserved. Old ways give way to better ways.

 

[Panther6834]

From what's been said so far it seemed a reasonable assumption that you'd have a router/firewall with a DHCP service. It seemed an honest assumption.

The Asus mesh system I was previously using did, albeit to a limited extent. The Asus "gaming" router I was using before that definitely did (plus a whole slew of 'dedicated' features & functionality that went away beyond any other router I've ever owned). Routers before that, honestly, I no longer remember. But, as for my current TP-Link DECO mesh system, no, it doesn't...at least, not in the usual sense. I was extremely tired when I typed that previous reply, so I didn't think of going into an explanation...but, I'll do so now.

With most routers, DHCP can be assigned manually to each device, plus you can 'reserve' a specific bank of IP addresses. In assigning on a device level, you can see a list of connected devices (shown by MAC address), to which you can look up & assign the IP it's currently assigned, or you can manually enter an IP of your own choosing. Additionally, of you know the MAC of a device you will be connecting, you can manually enter/save the data, in advance.

First thing to note is, setting up the router MUST be done via an app. Once set up, some configuration can be done via a Web browser...but, it's limited. Only through the app do you have full configuration control. Second, the TP-Link DECO does have something similar (almost identical) to DHCP...but, it works in a slightly different way (and, it's one of those things that can only be set up through the app). Instead of being called "DHCP Service", it's called "Address Reservation". When you first get to the screen, it's mostly a blank screen, work a '+' symbol in the upper-right corner (appropriate for a mobile app). When you click the '+', you are taken to a screen where, as with traditional DHCP, you see a list of currently-connected devices (if a device is 'off', but physically connected, the router does NOT see it as "connected"), showing the device name, MAC, and currently-assigned IP. To the left of each device, there's a checkbox. By 'checking' each device you want to add to the "Address Reservation" list, and then clicking 'Save', you've effectively done the same thing that DHCP does...but, unlike with DHCP, you can not manually assign an IP to any device showing in the 'connected' list, nor can you manually enter data for a device you will be connecting. You are limited to ONLY using the IP currently assigned to each listed device. Obviously, the way around this (if you want a specific IP) is to first assign a Static IP to the device (as I did with the DS918+), and then 'select' that device & IP from the router's "Address Reservation" list.

As I said, it's very similar to DHCP...but, it's not truly the same as DHCP. On the 'plus' side, in the end, it does allow you to achieve, essentially, the same results. That said, on another screen, there is a (sorta-kinda) DHCP, where it allows to to reserve a bank of IP addresses...but, it is completely independent from the "Address Reservation" list. If you were to first create a bank of IPs (before devices are attached that might end up with an IP within that range), you can NOT add (through the "Address Reservation" list) any devices to an IP within that range...because, as covered above, you can not manually assign any IPs. The whole process is a bit of a "workaround"...but, in a manner of speaking, it's actually simpler, and more "straight forward", than traditional DHCP.

 

[Panther6834]

Old ways die hard. Setting a fixed IP on the device does not prevent the router from giving that IP to another device, unless your router permits you (and you have made the effort to) restrict the router's DHCP range.

Additionally, when your change routers, or ISPs, and use an ISP router, you're likely to find yourself unable to connect to devices which were IP locked. For the NAS, this often mean a reset.

Reserving IPs within the router is convenient. In that manner, the IPs of all devices are centrally managed by the device that hands out IPs (obvious, huh?), and not scattered among the various devices (of which the administrator may not have ready access). Additionally, regular router settings backups help ensure the IP settings are preserved. Old ways give way to better ways.

Right now, due to my current living & work situation, I have no choice but to use an ISP's modem. Normally, I do not...partly because I don't like "renting" a modem, and partly because I don't care for the 'limitations' most of them impose (give me a Cisco or Motorola SurfBoard modem, and I'm quite happy).

As for the "changing ISP/modem/router" matter, than I'm more than 'familiar' with. It's, unfortunately, one of those "necessary evils" that you just learn to deal with, and you deal with it in whatever you consider the "best" was possible. I try to minimize the 'problem' in two ways. First, when switching routers, I set the new router up using the same SSID & password, which allows all devices to instantly connect once the new router is operational. Second, I maintain an MS Word document listing all devices, their MAC, and their current IP. This makes it much easier to get everything "secure" much quicker.

Now that that's covered, can we get this thread back on-track...remember, the "two NAS, one network" matter?

 

[Telos]

remember, the "two NAS, one network" matter?

Hasn't that been solved many times over in all these posts? It's rather basic, and here we are two pages in

 

[fredbert]

'Two NAS ...' was getting rather long and convoluted.

Basically, if you are running only Plex on one NAS then that can be done since it doesn't share any TCP or UDP ports that would already be needed for external access to the first 'data' NAS. So you don't need to consider reverse proxies: whatever port forwarding you are doing to the current 'data' NAS will remain; for the new Plex NAS you need to port forward to it, Plex's default port is TCP 32400. When you are using Plex apps you connect to plex.tv and it will then direct the app to the Plex service on the NAS.

Have you got the second NAS now? Or is this still working through permutations?

If you want to test networking concepts before buying the new NAS, you can use Virtual Machine Manger on the DS918+ and install Virtual DSM 7. With this it will appear like a second NAS on the LAN and you can install packages on it. As a test you only need to reserve a small amount of storage to the vDSM's storage pool. Once finished testing you can delete it all and the reserved storage will be released.

 

[Panther6834]

'Two NAS ...' was getting rather long and convoluted.

Basically, if you are running only Plex on one NAS then that can be done since it doesn't share any TCP or UDP ports that would already be needed for external access to the first 'data' NAS. So you don't need to consider reverse proxies: whatever port forwarding you are doing to the current 'data' NAS will remain; for the new Plex NAS you need to port forward to it, Plex's default port is TCP 32400. When you are using Plex apps you connect to plex.tv and it will then direct the app to the Plex service on the NAS.

Have you got the second NAS now? Or is this still working through permutations?

If you want to test networking concepts before buying the new NAS, you can use Virtual Machine Manger on the DS918+ and install Virtual DSM 7. With this it will appear like a second NAS on the LAN and you can install packages on it. As a test you only need to reserve a small amount of storage to the vDSM's storage pool. Once finished testing you can delete it all and the reserved storage will be released.

Thank you for the suggestion. I still only have the DS918+ (although, if it proves "doable", I'm extremely close to ordering the DS425+), and I haven't set any port forwarding. As for VMM, I've never used it. Even within Windows, I've never seen up a virtual box, so I know nothing about such...but, as I said above, I'm willing to test the idea, if it truly acts no differently than two physical NAS. But, first, is there anything I'd need to know in regards to setting it up & configuring it? For example, does it get assigned a separate IP & virtual MAC? While I'm awaiting your reply, I'll be in the DSM, seeing what I might be able to figure out on my own.

 

[Panther6834]

Hasn't that been solved many times over in all these posts? It's rather basic, and here we are two pages in

Being told to "use reverse proxy" is one thing. Providing a few lines of data to be entered in relation to reverse proxy is also one thing. But, when the person on the other end (me, in this case) knows nothing of what's being said, then, technically, the answer to your question is "no". Tho, based on the majority of your previous replies, gotta I could have expected such a comment from you. Previously, you "apologized" for your previous bashing...tho, you 'blamed' it on a "language problem"...yet, here you are, doing the same thing. As I asked you once before, if you're going to do that, please, REFRAIN from posting. Helpful information is greatly appreciated...derogatory information is not only unnecessary, it is unwanted & unacceptable.

 

[Panther6834]

'Two NAS ...' was getting rather long and convoluted.

Basically, if you are running only Plex on one NAS then that can be done since it doesn't share any TCP or UDP ports that would already be needed for external access to the first 'data' NAS. So you don't need to consider reverse proxies: whatever port forwarding you are doing to the current 'data' NAS will remain; for the new Plex NAS you need to port forward to it, Plex's default port is TCP 32400. When you are using Plex apps you connect to plex.tv and it will then direct the app to the Plex service on the NAS.

Have you got the second NAS now? Or is this still working through permutations?

If you want to test networking concepts before buying the new NAS, you can use Virtual Machine Manger on the DS918+ and install Virtual DSM 7. With this it will appear like a second NAS on the LAN and you can install packages on it. As a test you only need to reserve a small amount of storage to the vDSM's storage pool. Once finished testing you can delete it all and the reserved storage will be released.

I got VMM installed, and I was able to create the virtual LAN, including installing VDSM. Still working on activation it, to gain access from PC. Once that's finished, I'll move some files to it, and test remote access. Will report back once testing is done...or, if I run into problems.