Followup to my earlier request for help concerning endless login loop: finally able to connect by moving ROCK to DHCP from previous fixed static address. Similarly Tidal login fails with the ROCK set to a fixed address but works when set to DHCP. Fixed address used to work - the change at my end is that I am now using a Ubiquiti UDM SE as my router. What do you believe is the issue as using a fixed static address for ROCK NUC worked fine previously? Thanks for your help.
Describe your network setup
Ubiquiti UDM SE router, Draytek Vigor 167 modem. ROCK NUC directly connected to port in UDM SE. All hard wired.
If the fixed address is configured on the ROCK, then it’s, well, fixed. This also includes a subnet IP range. Your new router may be using an entirely different subnet range, and the fixed address may not work anymore.
Fixed addresses are normally not a good idea for this very reason: it requires diligent management whenever something changes in the network.
You can achieve the exact same thing (the device always using the same address) with fewer problems with DHCP by reserving an address for the device on the router.
Thanks for coming back on this - the subnet is the same and in fact the IP address is identical, only the setting on the ROCK was changed from static to DHCP.
Using previous BT supplied Hub, simply making an address reservation was not sufficient to guarantee that a given address would not be reused - the Ubiquiti may be more reliable in this respect, I have only just started using it a week ago.
One thing I did notice was that initially when the ROCK NUC was connected to the UDM SE, the device was not visible in its device table despite the fact that I could access ROCK fine via it’s IP address. Even manually entering the ROCK MAC address within the UDM SE device resulted in a greyed out blank entry, it only came alive when ROCK was set to DHCP on it’s home page.
The above seemed strange, just trying to understand what is going on as something is getting blocked unless ROCK is set to DHCP and this was not the case previously.
I’m pretty sure nothing is getting “blocked”… just enable DHCP and let it take care of itself. If you need to reset ROCK to use DHCP, connect a keyboard and type resetnetwork (no spaces).
If the BT router didn’t manage DHCP reservation, then it was broken somehow. It’s a basic functionality that simply has to work in any even half decent router. It’s weird and I’d bet this works with the Ubiquity.
If the subnet is OK, it’s possible that the Ubiquity assigned the same address as the fixed one to another device, hence causing an address collision, unless you excluded it on the router from the DHCP range.
Having looked into it further, I believe the issue was that I had the Gateway field set wrong in ROCK, it was pointing to the old BT value and needed to be changed to the new gateway address for the UDM SE which was different.
Hence, I could reach the ROCK home page but it could not reach the Internet nor the roon servers. By correcting the Gateway field, it now works as expected even when set to static IP.