How to access NAS which is outside the subnet pool

johnpd · May 8, 2026

I bought a new router and it has a different DHCP pool range from my old router. Old = 192.168.1.2 - 192.168.1.128; New = 192.168.0.2 - 192.168.0.253. I had two NAS devices set at 192.168.1.81 and 192.168.1.82. I can actually access these through Windows, but they do not appear on the router's device list. I have a third NAS which does show on the device list which also had a fixed IP assigned to it, but I might have used a different method to do the assignment. These are all Synology NAS devices. If I try to change the range on the new router to include the two missing NAS devices, it does not like it. Is there some way I can change the assignment of the NAS devices outside the normal range? Here is the current setup.

JohnD

gunrunnerjohn · May 8, 2026

Well, you're going to have the NAT layer to contend with. Why not turn the secondary router into an AP? What's the purpose of the two routers?

hsehestedt · May 8, 2026

John, Forgive me if I'm not understanding the scenario entirely correctly here O let me summarize my understanding: You have a router that you're replacing with a new router but that new router uses a different address pool. The question is how do you adapt your network to handle this range of addresses that your router is programmed to hand out. Is that about right?

If I got that right let me ask this question: why don't you simply change the range of addresses that your new router is handing out to be the same range of addresses that the old router handed out? I know that you said that you already tried to change the range of addresses so that it would cover the range of addresses that the NAS devices have but are you actually doing this properly? In other words are you supplying a valid subnet range You can't just stop At any random address you need to make sure you're covering the entire subnet for example the entire 192.168.X.X address range Or subdividing that further but with valid binary increments.

I'm not going into more detail yet because I'm not sure if I'm even properly addressing your question so for now I'm just waiting to hear feedback from you as to whether I'm properly understanding your situation or not.

gunrunnerjohn · May 8, 2026

I read that wrong, if there's only one router involved, I like the suggestion by @hsehestedt as that should solve the whole problem!

S0C9 · May 8, 2026

hsehestedt said:
John, Forgive me if I'm not understanding the scenario entirely correctly here O let me summarize my understanding: You have a router that you're replacing with a new router but that new router uses a different address pool. The question is how do you adapt your network to handle this range of addresses that your router is programmed to hand out. Is that about right?

If I got that right let me ask this question: why don't you simply change the range of addresses that your new router is handing out to be the same range of addresses that the old router handed out? I know that you said that you already tried to change the range of addresses so that it would cover the range of addresses that the NAS devices have but are you actually doing this properly? In other words are you supplying a valid subnet range You can't just stop At any random address you need to make sure you're covering the entire subnet for example the entire 192.168.X.X address range Or subdividing that further but with valid binary increments.

I'm not going into more detail yet because I'm not sure if I'm even properly addressing your question so for now I'm just waiting to hear feedback from you as to whether I'm properly understanding your situation or not.

That was my first thought too..
Change the DHCP address range back to that used by the original router (not sure why it stopped at 128 tho'?) and.. bingo! Problem solved!

johnpd · May 8, 2026

It won't let me do that. I am wondering if I have to change the default gateway first, then change the pool range to correspond to the gateway?

JohnD

S0C9 · May 8, 2026

johnpd said:
It won't let me do that. I am wondering if I have to change the default gateway first, then change the pool range to correspond to the gateway?

JohnD

Yes. You'll first need to change the routers BASE IP - they usually arrive as 192.168.1.1
idk why your 3rd node = 0.
Default DHCP settings are based off that base IP and are (unless user modified) in the range of 192.168.1.2 - 192.168.1.255

Gateway would be: 192.168.1.1
subnet mask: 255.255.255.0

glasskuter · May 8, 2026

@hsehestedt is the man when dealing with networking.
I'm a safety gal and here's the way I would accomplish doing what he said.

1.Turn off all devices in the network including printers.
2. On router disconnect cable from INTERNET (poe) port.
3. Connect only one device to the router using an ethernet cable to one of its ETHERNET ports, access router configuration and change its ip and address range. ( SSID. too, if you want to keep what was being broadcast from the old router.) Save configuration. Restart the router.
4. Reconnect POE cable back to Internet port on router.
4. Reconnect each device one at a time. I would also probably go so far as to reset networking in each device.
Overkill? Maybe. But I'm a better safe than sorry gal.

johnpd · May 8, 2026

1. That would be difficult. I have too many to shut off including a number of IoT devices. I can disconnect all devices from the router fairly easily as I have two cables going to wired computers and two cables going to switches which handle everything else.
2. You are saying disconnect the router from the modem?
3. I can easily connect one of the wired computers. I assume I need to change the default gateway and the IP address pool as shown on the screen print above? I don't want to change the SSIDs as then I would have to change all the devices that are connecting to the network. I am just using the original 2.4 and 5Ghz SSIDs.
4a. Reconnect back to the modem.
4b. It would be easier to reconnect one switch at a time to see if that works. It looks like I have about eight devices spread among the two switches.

JohnD

S0C9 · May 8, 2026

@johnpd - I don't believe you need to shut them off, but a simple disconnect of the switches from the main router would suffice - since they aren't working with static IP's anyway.
Once you've change the primary router's IP, (probably requires a power cycle/restart) then DHCP should start assigning addresses and your NAS devices w/ static IP's should start showing again on the network.
Devices previously assigned IP's on the old 0.1 network should automatically refresh on the 1.1 network.

johnpd · May 8, 2026

OK, it looks like I got everything back. I was able to get a hold of TP-Link support and the support person said all I had to do was change the default gateway IP address and the router would resolve everything else. So that is what I did and now it looks good.

Thanks all for your help,
JohnD

garlin · May 8, 2026

S0C9 said:
Yes. You'll first need to change the routers BASE IP - they usually arrive as 192.168.1.1
idk why your 3rd node = 0.

The entire network address space of 192.168.0.0 thru 192.168.255.255 is considered "private" network space.

Whether your router's IP defaults to 192.168.0.1, 192.168.1.1, 192.168.2.1 or whatever is simply a convention.

The last two octets can be whatever you want, and different manufacturers can use different default IP addresses. If you have an older router that you're replacing, many times it's easier to go with what network IP's you had before, so you don't have to make too many changes on the network clients.

S0C9 · May 9, 2026

garlin said:
The entire network address space of 192.168.0.0 thru 192.168.255.255 is considered "private" network space.

Whether your router's IP defaults to 192.168.0.1, 192.168.1.1, 192.168.2.1 or whatever is simply a convention.

The last two octets can be whatever you want, and different manufacturers can use different default IP addresses. If you have an older router that you're replacing, many times it's easier to go with what network IP's you had before, so you don't have to make too many changes on the network clients.

Thanks, but I’m well aware of the 3 privates network classes and network structures. I did NOT know how much network knowledge the OP had (based on his post) so I kept it simple.
I could have said 192.168.1.0/24 but wanted to avoid going down the CIDR rabbit hole.

How to access NAS which is outside the subnet pool

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

aka Mama Glass

My Computers My Computers

At a glance

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

Well-known member

My Computer My Computer

At a glance

My Computer

My Computers

My Computers

My Computers

My Computer

My Computer

My Computer

My Computers

My Computer

My Computer

My Computer

My Computer

My Computer