I want to map several drives in my home network because the Windows 10 networking always seems flakey in my hands - resources that are there don't always show up etc. I have found that mapping network drives is far more reliable and actually shows me what is connected.
So here is the question. I can go into my Ignite Modem and SEE the IP address of each of the computers on my network and I can use that to successfully map lots of network resources. How "consistent" are these IP addresses going to be? So, if one of them (the one I'm typing this on for e.g.) is 10.0.0.183, and I use that IP for mapping purposes, is the DHCP function going to change that randomly? So far the IP address connections seem consistent and stable, but I wonder if I should be assigning each of my network PCs a "reserved IP" just in case?
If I do that, can I just use the current IP (say the 10.0.0.183) and make it reserved instead of DHCP or do I need to pick from a whole other set of IP addresses that can be reserved?
Do both. I have my static IPs with several devices (NAS, server, printers) within the router ip range. Assign the ip at the device and reserve it in the router.
That is a good way of using a static IP address that is within the DHCP scope. However, if the device itself does not use DHCP when it connects to the network and register itself with the gateway, it won't be able to take advantage of a unified DNS/DHCP implementation on the gateway, which would otherwise help to make accessing resources on that device by name more reliable.
The other problem is that the device management options in the Ignite WiFi Hub are limited and quirky, and that may also be part of the problem why accessing resources by name may not always work for some network clients.
Which also makes the point that I was trying to make (re: the advantages of having a device connect using DHCP vs using a static address) somewhat moot. 🙂