Mac Mini Fails to Recognize MacBook Pro as Core (ref#OBK7OX)

What’s happening?

· I'm having trouble connecting to Roon

What type of connection issue?

· Something else

How can we help?

· None of the above

Other options

· Other

Describe the issue

I am running Core on a dedicated Macbook Pro late 2013. It is wired ethernet to the router and is only a Server. I have a 2024 Mac Mini M4 in my office. On the Mac Mini, I downloaded Roon, but when you select a server it says This Mac but that is not this computer it is actually the Mackbook Pro. I have never set this computer up as the Core.
If you notice the OS is 11.7.10 which is Big Sur. This computer is running Sequia 15.3.1. Previously I was using the 2012 Macbook Pro and the Mini recognized it and had no issues. The Mini replaced the 13 Macbook Pro, so I repurposed it as the core, hoping for better performance.

Settings>Audio - the Mac Mini is not present. This Mac is actually the Macbook Pro. I even tried to airplay to the Mini but that does not work either.
The Dac shows up on the Mac Mini under Sound, but not in Room, beacause this Mac is not this Mac but rather the Macbook Pro Core. I have uninstalled and reinstalled, toggled Privacy and Security>local Network>Roon on and off and back on. Disconnected the Server and rebooted twice, but no success.
I have rebooted both the core and Mini but no luck.

That was the original issue but I have a new scenario. I went to privacy>Local Network and toggled off Roon. I then reinstalled and click make this computer the server. I then disconnected it and toggled Roon back on in Privacy. It now recognizes the Mac Mini As an option and my old Caps 3 dedicated media player that was my core a long time ago. It will not recognize the Macbook Pro I am using as the Core on every other End point. I have an Ifi Streamer, Caps 3,and a 2015 Macbook Air as end points that all recognize the Core Macbook Pro. The only one that does not recognize it is the 2024 MacBook Pro Mini.

Best setup Configuration ?

I am assuming this is the best setup option. I upsample everything to 24/192 and use precise/ minimum filter I believe. I could use the CAPS V3 as the Core, but it is also playing to my main system. I could also use the Mini as the Core, but it is wifi and not wired. I can move an extender next to it and wire it there, but I do not believe that would be nearly as stable as wired to the router.

Thank you for your help

Describe your network setup

Google Fiber 1G, Router-Google- GR6exx0c

Hi @david_leitner,

Thank you for your post.

Diagnostics show the Mac Mini on the same subnet as the rest of the Roon environment, which is good. The issue here is likely with device announcements - it sounds like they aren’t getting through from the RoonServer (hosted on the MacBook 2012) and the Mac Mini in your office.

Do you have any mesh nodes, switches, or access points between the hardwired MacBook server and the Mac Mini? If so, ensure multicast forwarding and IGMP snooping are enabled.

What about antivirus software or third-party firewalls installed on the Mac Mini?

Let’s start by removing the server instance installed on the Mac Mini and installing only the GUI:

  • Exit out of RoonServer
  • Navigate to your RoonServer’s Database Location
  • Find the folder that named “RoonServer” and delete it
  • If there is a folder named “Roon,” then you should still have the Remote installed
  • If there is no “Roon” folder, visit our Downloads Page to install Roon Remote again on the Mac Mini.
  • Restart RoonServer on the MacBook to initiate a device discovery cycle
  • Open Roon on the Mac Mini

Do you see the original server (MacBook) available?

It initially wirked for all but 1 endpoint that started doing the same thing. The 2012 Macbook said this mac but it was the 2013 Macbook pro. I did the same step here deleting the roon server file.

Then the core 2013 Macbook Pro failed. It now says there is an error loading your library. To avoid loss restore a back up and will not load.

Now they are all down

Sorry to be a pain but keeps getting worse. I uninstalled and reinstalled tge core. Everything worked great until I hot yo the Mini. It recognizes the Core niw great. BUT it crashes it. I get warnings focus failed then library liading error then it crashed the entire ststem. Now i have uh oh something wrong on all the computers.

Went back to the core does not recognize itself says do you want to set this computer up as the server.

I restarted the computer and it comes up but now says there was an issue loading your library. I uninstalled and reinstalled but same issue.

I restarted and reinstalled again it is back up on the core but only the CAPS and Ifi work. Others keep coming up with there is an issue loading your library.

I deleted all the roon files in Library and reinstalled. Everything is working except the Mini.

Scared to touch the mini.

Hi @david_leitner ,

Thanks for the update and for letting us know that you were able to reinstall to get past the library loading issue. I’ve enable diagnostics for your account and I am not seeing any corruption traces at this time.

Did you by any chance use Time Machine / Migration Assistant to transfer the Roon app over?

Just to clarify here, the Mini is crashing and still getting loading library errors?

Mac Mini endpoint thinks it is a different computer (the server)

I have a MacBook Pro as the dedicated server.
I downloaded Roon on a Mac Mini. I deleted the Roon Server File. It shows the MacBook Pro as the Server. It shows the correct artist and tracks

However, when you go into settings this Mac is actually the Server. If you play from here the sound comes out of the Macbook Pro Server ??? I have 4 other points all working correctly.

Any idea how to get it to recognize itself?

Thanks

Hi @david_leitner,

Can you clarify if RoonServer is still running on this Mac Mini in the Menu Bar? If RoonServer is running in the background, make sure the option to launch on startup is deselected.

Diagnostics do indicate that a RoonServer instance is still hosted on the Mac Mini, but there’s not a corresponding RAAT instance. This probably explains why local playback is not available on the Mac Mini.

You’ll need to fully sign out of Roon and desociate Roon Remote from the Mac Mini server before you delete the RoonServer folder. Otherwise, Roon will simply relaunch the server on startup.

From there, double-check that Roon has local network access permitted in Privacy & Security settings on the Mac Mini.

RoonServer was still running on this Mac.

I probably did this wrong but, it did not work.

I deselected startup.
I signed out of the Core, Disconnected the Mini(Hopefully this is what you meant by dissociate Mini), then Deleted RoonServer File.

Unfortunately, it still shows 59000 tracks but this Mac is still the server.

What did you mean by dissociate the Mini? How do I do that?

Thanks

Hi @david_leitner,

Open the Roon settings → General page. At the top there will be a box saying Roon Server with a disconnect button in the corner. Click that and then you will be able to proceed with @connor’s instructions.

Please let us know if you require any further assistance. We are here to help!

Ok that is what I did.

I just tried again, but no luck.

The RoonServer file is no longer on the computer but under Privacy & Security on The Mini, Roon has local permission but there is an option for RoonServer as well, and it is off. Do not know if this helps any but was surprised to see RoonServer option here.

The mini is driving me crazy. I cannot figure out why it connects to the server library but things it is the same computer.

Hi @david_leitner ,

I will send you a private message with an advanced troubleshooting step, please let us know if that helps.

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