Switched from 2018 Mac Mini w/Intel chip to Mac mini M4. M4 does not recognize all of my devices. Switched back to 2018 Mac, and now it now it no longer recognizes all of my devices either, specifically dcs rossini, which is connected to my amp and pre amp. How to get roon recognizing the Rossini again, which it had done for years? Mac Mini is running OS Sonoma. Thanks!
Describe your network setup
2018 mac mini running sonoma. Connected to dcs Rossini, connected to to verizon routers and audioquest power conditioner. For years, it has plyed through macintosh amp and preamp. that's what is missing. now it only plays through system out put and macbook pro speakers
Thanks for reaching out. I am looking over your account diagnostics and it looks like for some reason your dcS is getting a different IP address range compared to your Macs. As the first troubleshooting step, can you please try to reboot your dCS, networking gear and Roon Servers to see if this helps?
Rebooted all, and now on the Audio page in Roon, I am seeing Roon with no Enable button and an IP address associated with the Mac Mini. How do I get the Enable button back for Roon?
Thanks for sharing the screenshot. I am looking over your account details and I am still seeing your dCS on a 169... address range. This usually happens when a device can’t get a proper IP address on the network. Have you made any changes regarding your network recently?
Is there any way you can try to find the IP address of them using another method (such as the dCS app)? Also please note that it is best if you reply using your @david.salsberg forum email, as you used that account to create this forum post and the troubleshooting history is properly tracked.
Please note that when I reply on this forum, I just click on Reply and it automatically uses David_Salsberg. If there is something else I should be doing instead, please let me know.
Please test out disabling your other local subnets within your network, and reboot your router. That should force all your Roon devices and remotes to land on the same local subnet.
So you did not use Time Machine at all between your Macs?
With that, do you have the Mac firewall active on the machine? It may be worth testing out disabling the Mac firewall temporarily to see if that resolves your issues, here’s more info on this:
The different subnet means that your Mac is on one IP address range while your dCS is on another address range. The issue I am seeing here is that the dCS seems to think it’s on a 169... address range, which is different than the rest of the network.
I would focus the troubleshooting effort on the dCS side of things, the Mac appears to be running normally as far as I can tell. I would try rebooting the dCS, router, trying a different Ethernet cable for the dCS. If you have two routers, this type of issue can also occur.
