Helpneeded, no servers found

Only thing I would add to the advice given is that it doesn't matter what IP address range you use at home, so setting your new router to the old address range is fine and there are no implications for anything your Internet Service Provider might be doing later.

If it were me, now you've got it working, I would leave it all alone.

best

David

Thank you all, for your kind help, this is, to me, a very big part of the Naim brand; The help everyone chips in with. And  for the record, I will leave things, as they are, for now :-)

There is one critical thing not mentioned that you should really know about if you decide to stay with your current setup of using the 192.168.1.x subnet (vs the 192.168.0.x default) and leaving your US in the static IP previously assigned (192.168.1.16) : you must look in your new router and chech the range being used for DNS assignment and make sure that 16 is not in the pool (eg set it to something me number bigger than 16, such as 192.169.1.101 at the low end and whatever you like on the high end, often 192.168.1.255). This allows you to use “low” numbers (below 100 in my example) for manually assigned static addresses and leaves high numbers (above 101 here) for automatic assignment by the router. Failing to do this leaves open the possibility of an address conflict with two devices having x.x.x.16 if the DNS hands it out ... and you really don’t want that! Also, stick a label in n the US to remind yourself that it has the static address for any future changes  

Although this can and does work (and was how you had to do things in the old days before Reserved addresses were a thing), you would be better to switch to completely automatic DNS management and then use the Reserved flag in your router to ensure that your US doesn’t move around. Someone explained this above and it’s the better practice for home users for lots of reasons (mainly that you are prone to forgetting custom setups after things work, haha). 

Good luck with your new home network. 

Regards alan

edit: I advise this since the DNS pool is usually set to start at x.x.x.10, so your choice of 16 is potentially a real problem 

I think you mean DHCP, not DNS.

alan33 posted:

There is one critical thing not mentioned that you should really know about if you decide to stay with your current setup of using the 192.168.1.x subnet (vs the 192.168.0.x default) and leaving your US in the static IP previously assigned (192.168.1.16) : you must look in your new router and chech the range being used for DNS assignment and make sure that 16 is not in the pool (eg set it to something me number bigger than 16, such as 192.169.1.101 at the low end and whatever you like on the high end, often 192.168.1.255). This allows you to use “low” numbers (below 100 in my example) for manually assigned static addresses and leaves high numbers (above 101 here) for automatic assignment by the router. Failing to do this leaves open the possibility of an address conflict with two devices having x.x.x.16 if the DNS hands it out ... and you really don’t want that! Also, stick a label in n the US to remind yourself that it has the static address for any future changes  

Although this can and does work (and was how you had to do things in the old days before Reserved addresses were a thing), you would be better to switch to completely automatic DNS management and then use the Reserved flag in your router to ensure that your US doesn’t move around. Someone explained this above and it’s the better practice for home users for lots of reasons (mainly that you are prone to forgetting custom setups after things work, haha). 

 

I agree that there is potential for an IP address conflict with this setup. That's why I suggested returning to regular DHCP operation. Then perhaps reserve an address for the US from within the original range, but this may not be necessary. 

johnG posted:

I think you mean DHCP, not DNS.

Argh. Of course! Thanks for the catch. 

If you've set your router IP to 192.168.1.1

Set your DHCP for a range of 192.168.1.20 to 192.168.1.50 that should be plenty of dynamic address allocations & allow for a further 17 static IPs as 192.168.1.16 will be occupied and out of the DHCP address range.