Roon on laptop unable to playback locally (ref#3J7NNX)

What best describes your playback issue?

· My DAC, streamer, or speaker doesn't appear as a Zone in Roon

What type of Zone is affected by this problem?

· *Directly-connected Zones* are affected.

Is your device connected directly to the Roon Server via cable or over the network, or is it chained through another device (such as a streamer, Roon Bridge, or Roon Remote)?

· Connected directly to my RoonServer machine

Does the device show up at all in Roon Settings -> Audio?

· No, it does not show up there

Does the device play audio from another source when using the same connection?

· The device has no problems with another audio source

Have you checked that Roon is whitelisted in any firewalls?

· I've checked the firewall and the issue remains

Since you are using a network connection to the device, please ensure that your RoonServer is on the same subnet as the device

· My devices are on a single subnet but is not visible to Roon

Do you have a complex network setup?

· I have a *mesh network* with devices connected to multiples points

Your local network might need some re-arranging to support Roon.

· None of the suggestions have helped me. I'd like to submit a support request.

What are the make and model of the affected audio device(s) and the connection type?

· 2.3 GHz 8-Core Intel Core i9

Describe the issue

Roon running on a single laptop. No local playback.

Describe your network setup

Google mesh network. But this is just on a single machine. I can playback on network devices but not locally.

Hi @Ian_Alderman,
Thanks for reaching out to ask us about this issue. Can you please navigate to macOS System Settings > Privacy & Security > Local Network , and make sure Roon is allowed. If it is already enabled, toggle it off and on again. Then reboot your Mac, and see if the same issue persists.

Another thing to check is that RAATServer is allowed through your firewall.

Access to the Roon app is allowed through the firewall.

The issue seems to be that there was an existing service running on port 9200. Removing that service and restarting seems to have fixed the issue.

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