Roon fails to recognize network devices consistently (ref#F71AVE)

[Bobolaclune]

What’s happening?

· Other

How can we help?

· None of the above

Other options

· Other

Describe the issue

Roon consistently fails to recognise devices on my network

Describe your network setup

Eero Mesh network, NUC Roon Server, MacBook Pro and MacBook Air

[Bobolaclune]

I have uploaded Roon’s Audio page to indicate that none of my devices are shown as available. I am also attaching a screenshot from Tidal clearly indicating all my devices. If Tidal can recognise my devices on the network , why can’t Roon? I have tried toggling the settings in Privacy>Local Network without success. Rebooting my Mac works… for a while before Roon reverts to showing no devices as available.

[benjamin]

Hey @Bobolaclune,

Thanks for writing in and sharing your report! As a next step in troubleshooting, can you please double-check your mac firewall settings to ensure Roon has proper access?

The easiest way to test this would be to temporarily disable your mac firewall and reboot your machine. Let me know if this changes any behavior for you.

Here’s more info around Roon and firewalls:
https://help.roonlabs.com/portal/en/kb/articles/firewall

Let me know if this helps!

[Bobolaclune]

I’ve switched off the Firewall and rebooted the Mac. FYI, my settings allowed Roon access. My devices are now available.

However - based upon past behaviour, this doesn’t last and Roon will then stop displaying my devices. IF this workaround works, then there is another more serious issue - I have no Firewall active on my system and that opens up all sorts of vulnerabilities to Malware and Phishing attacks.

[daniel]

Hi @Bobolaclune,

You’re absolutely right — leaving the firewall off isn’t a viable long-term solution. We only recommended disabling it temporarily to confirm whether it was contributing to the issue. Now that we know it is, you should definitely turn it back on.

The best next step is to create exceptions in your firewall for Roon’s processes so they can communicate properly. The two processes you’ll want to allow through are Roon and RAATServer.

If you need help setting that up or would like step-by-step instructions for your firewall, just let us know. We’re happy to assist!

[Bobolaclune]

Hi Daniel

Well, as expected, that workaround only worked for 24 hours , I am now back to the same situation. I think I have already followed the instructions to create exceptions
for Roon & RAATServer. Screenshot attached.

So to reiterate, these exceptions were already in place. No devices are showing up after I switched the Firewall Off & toggled it back on. Only option left is to reboot my computer (I have 8 different applications open so this is a giant pain) but that solution is really only good for 24 hours or so.

Thoughts?

Shodhan

[Bobolaclune]

As a further clarification, rebooting my Mac always provided a short term fix and RAATServer and Roon were always permitted through the Firewall so really, nothing has changed or improved the situation. I would really like to understand why Tidal recognizes all my devices (all the time), while Roon has this issue.

Thanks

[noris]

Hello @Bobolaclune ,

@Bobolaclune

Eero Mesh network

Since you have an Eero network, I wonder if it is creating a separate subnet for your devices. Roon only works properly when the devices are on the same subnet, and I’ve seen instances before of it making an additional .5/.7 subnet. If this is the case on your end the easiest way around it is to set Reserved IP addresses for your devices.

[connor]

Hi @Bobolaclune,

We wanted to reach out since this thread hasn’t had any activity from the original poster in some time.

Please see the above comment from my teammate concerning Eero mesh networks - specifically, firmware updates can prompt Eero devices to delegate certain IP addresses to a separate Class-C block, interrupting Roon’s device discovery multicast traffic.

See here for more information: https://help.roonlabs.com/portal/en/kb/articles/eero-mesh-networks-with-roon#Try_rebooting_the_Eero_router

We’re eager to help resolve this issue - keep in mind this thread will auto-close without a response in just a few days, however. Thanks!

[Bobolaclune]

I have followed all the instructions in the link you included about re-configuring the Eero’s settings without luck. Here is the suggestion from Eero:

" Regarding on your question yes we can try to adding a IP reservation on the devices that are affected and here the steps on how you can do it.

Add IP reservation.

• Open the eero app: and go to Settings.
• Tap on Network Settings .
• Select Reservations & Port Forwarding .
• Tap on Add a reservation .
• Choose to select an existing device or enter details manually .
• If selecting an existing device, you’ll be prompted to enter the IP address you want to assign to it.
• If entering details manually, you’ll need to provide the device name, desired IP address, and MAC address (found in
• the eero app under the device’s IP address details).
• Save the changes."

Thoughts?