Connecting PCs to new wired network

I'm adding a secondary router to our Verizon FiOS router in order to isolate certain computers from the rest of the network. My question is: will I need to turn off the computers that are to reside on this secondary network, or can I simply leave them turned on, plugging them into the secondary router (after setting it up) and they'll find the new network without complications?

In case it matters, three points:

1. There will be NO wireless connections anywhere
2. All computers are running Windows (various flavors), except for one that's Linux
3. The proposed arrangement is as follows:

ONT --> FiOS G-1100 Gateway router
FioS router Ethernet LAN port 1 --> network switch --> PCs on 'main' network (unchanged)
FioS router Ethernet LAN port 2 --> secondary router --> other network switch --> PCs on 'secondary' network

The secondary router (a TP-Link TL-R470T+) would be connected from its WAN port to the second Ethernet port on the FiOS router.

The only difference between this new arrangement and the current one is the addition of the secondary router; right now, LAN port 2 on the FiOS router is connected to that other network switch.

So, to repeat, the question has to do with whether I need to turn off the PCs that will go on the secondary network and then turn them back on once the secondary router is set up and all the Ethernet cables are hooked up; or whether I can leave the PCs turned on and they'll just find the new network when I move the connection from the FiOS router to the TP-Link router.

Thanks a bunch for any help/tips.

 

They should just connect when you attach the cables.

 

You might need to do a simple reboot so they can pickup their new IP address assignment.

 

Thanks, so I'll first make the switch with the PCs still turned on, and then reboot if needed.

 

Or click on the network connection icon in the tray, and disconnect/reconnect.

Or in Linux root terminal:

Code:

ifdown eth0
ifup eth0

Or in Windows:

Code:

ipconfig /renew

 

Which reboots the computer anyway.

 

Thanks for your help @mirimir and @Bill_Bright -- the change went through without a hitch.

 

Huh? I've never seen that. Is it a new thing in Windows?

 

Great! Glad it worked and thanks for posting your followup.

Ummm, pretty sure its been that way for many years. I only have W10 here but if you click the network icon (there is no disconnect/reconnect, BTW) and click on "Status", you will see the option "Network reset". Follow the prompts and you will see the following,

 

Not a Windows 10 option. The simplest advice I would give would be if it doesn't just work, reboot. A network reset may have you looking for drivers with no network access to download them if they are not included in Windows 10. Not an issue for most modern hardware but not a fun day if you require drivers that need to be installed from the manufacturer.

 

@Bill_Bright -- Ah. Learned something. Never used Windows 10. Seems like a horrible change.

But the ipconfig command still works, right?

 

ipconfig's still there.
I believe mirimir was referring to disable/enable network adapter. That would prompt DHCP to issue an address to a NIC. Maybe disconnect/connect was once there, on XP, can't remember.
But even this should not be needed, a cable reconnect would also set ARP in action.

 

Not at all. W10 is much better in almost every way - once you get used to the changes.

I know - but he said through the system tray icon.

 

He did. And you can access the NIC by r-clicking a tray icon -> 'Network & Internet setttings' -> 'Change adapter options'. It's a bit of a long path but I kept this habit from XP days where you had one click less to access the NIC. iirc.
But I generally share your sentiments regarding W10.

 

Yeah, you are right. You can disable it from there. My mistake. Worth a try.