Roon unable to detect booted Roon Ready device on network (ref#X52RDI)

Hi! What’s not quite right with Roon?

· None of the above quite fits

None of the above quite fits

· None of these quite match

Tell us what's going on

· Roon does not find booted up Roon Ready audio device on network although it finds another Roon Device on network. Device is detected by Music Server OS on Network, but Roon can't find it . Help. Thanks.

Tell us about your home network

· No VPN. Hardwired network. Linksys Velop WHW03V2>Netgear GS108>wired shielded ethernet>Trendnet TEG-S51SFP>fiberoptic cable>Sonore Signature Rendu Deluxe. Small Green Computer Roon Server is connected to the Netgear GS108. Another Roon endpoint: Cary iOS All in One Player DAC Amp is connected to theTrendnet via ethernet and Roon is able to find it and play music. Roon is not finding Sonore on same Trendnet switch. Only difference is Sonore connected by fiberoptic from Trendnet switch and Cary by wired ethernet. Both are booted, visible and connected on the network view on MacBook. The computers can see the Sonore device, Roon cannot.

Hello,

Thank you for reaching Roon support

macOS Sequoia (version 15 and higher), has tighter (and more obfuscated) network security settings than preceding MacOS versions.

Can you please navigate to macOS System Settings > Privacy & Security > Local Network, and make sure Roon and Roon Server are allowed.

If it is already enabled, toggle it off and on again. Then reboot your Mac, and see if the same issue persists.

I fixed it. Suspected Roon and I was right. Deleted desktop Roon App from my MacBook. Downloaded App from Roon again and reinstalled. New installed Roon App when launched found ALL devices on my network, including the missing Sonore player. Thank you.

Hi @Michele_Jacquin,

The MacOS Sequoia network security settings will intermittently lock out RAATServer’s access to the local network. This occurs widely with audio apps that depend on the loopback connection, not just with Roon.

Reinstalling Roon is just rolling the dice again - it’s really worth taking the step @vadim suggested to ensure that MacOS doesn’t interfere with device discovery again after the next Roon or system update.