Roon app on M1 iMac cannot locate Nucleus+ after IP address change (ref#J205QY)

What’s happening?

· Other – My issue isn’t listed above

Describe the issue

The Roon app on my M1 iMac cannot locate my Nucleus+. They are on the same network and I just updated MacOS to 26.2. Also, the IP address was changed to 10.0.43 from the "standard" 192.168.1.1. Nucleus+ can be seen by Orbi but not Fing. It shows up as 192.168.1.31.

Describe your network setup

Router is Orbi RBR850, with one satellite. Switch is TL-SG116E. Modem is a Spectrum E31T2V1 cable modem. I installed an AT&T wireless modem, but disconnected it almost immediately. This may have changed the ISP addresses system-wide. Also, I had just upgraded to MacOS 26.2 from 26.1 that morning. Computer is a 2021 M1 iMac.

That isn’t done by the devices on their own volition but by your router / DHCP server. You must make sure that all devices connect to the same router (by Ethernet cable) or are in the same wifi network, and that the router puts the wifi on the same network as the Ethernet.

These three things can’t be true at the same time:

If one device is on a 10.* network and the other on 192.*, then they are NOT on the same network.

Also, which device was changed to 10.0.43?

I suspect that switching from the Orbi to the AT&T Air modem caused the change; while I can’t prove it, everything went haywire (in the sense that nothing seemed to be responding on the network) after the AT&T modem was removed and the Orbi re-installed. 10.0.43 is the iMac. Every device on the network except for the Nucleus+ was changed to the 10.* ISP. I agree that everything is on the same network, it has been ever thus, until the ISP was changed.

This is a correction of my previous post: namely, I replaced Spectrum’s cable modem with AT&T’s Air (wireless) modem. I didn’t change the Orbi, except to change locations. Once everything was restored, the Orbit and the Spectrum devices were returned to their previous locations. Sorry!

Make sure that you have only one WiFi access point and one DHCP service running, not duplicate ones on the different devices.

Hi @Mike_Contreras !

We were just able to retrieve a little piece of analytics data from your system.

We can see that now your mac and nucleus are in the same network and seem to be connected fine.

Can you please confirm that ?

If not, can you please share with us a screenshot of how the problem looks like and a time stamp (exact time & date) of when did you try to connect ?

Thanks!

Regards.

Everything is in good order, again. This incident gives rise to the question: is there any procedure for changing the IP address of the Nucleus+ via a standard web browser? As I noted earlier, the IPs were changed to 10.* format when I changed (temporarily), ISPs. There was no way to change the Nucleus+’s IP. That’s what caused the furor. Regardless, thanks for being there. I appreciate it. Cheers! Mike

As mentioned, normally the IP addresses are not chosen by the devices but centrally assigned by the DHCP server on the network. Therefore, there is normally no need to change the IP address on the Nucleus directly (or on other devices)

In home networks, there is normally just one DHCP server on the network that provides this service. It is usually located on the router, and it ensures that all devices receive an IP address on the same network.

Every device sends a DHCP broadcast request on the network, which is essentially “hey, I am the device ABC with MAC hardware number XYC, is there a DHCP server here that can give me an IP address?”. The DHCP server then sends an answer on the network, stating something like “Hey, to MAC number XYC, I am the DHCP server at 192.168.1.1, please use the IP address 192.168.1.100 from now on, and 192.168.1.1 for the Gateway”.

If one installs more than one router, or additional wifi access points, they may have their own DHCP server running by default, which creates havoc because the devices end up on different networks. The administrator must turn off (usually) these additional DHCP servers.

(Side note: In the web admin interface of the Nucleus, one can turn off the DHCP requests and assign a static IP directly on the device, but this is NOT recommended as the device can become inaccessible if anything changes on the network. When using static IP addresses, the admin must be extremely cautious, and nobody with a clue does this unless in very specific situations)

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.