Failed To Recognize Windows PC as Zone Audio Device

Core Machine (Operating system/System info/Roon build number)
Nucleus Core; Windows PC OS10 Remote Roon SW
TEXT GOES HERE
Nucleus Core; Windows PC OS10 Remote Roon SW, Roon 1.7 for both Core and Remote
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

Wifi using router. Music files on QNAP network server, connected directly to Roon Nucleus, no audio to Remote Roon audio sourc. Source is directly connected to the Windows Laptop but two network servers and their devices, A Roon Ready Oppo 205 and a Marantz receiver are all that shows.

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
Roon Core has Oppo 205 Device which works properly

*Description Of Issue remote Roon ver 1.7 software works fine on my Windows 10 laptop, listening to the Oppo 205 audio device connected in Room 1 with headphones connected to Oppo205. However, when I move the laptop to another room which is beyond the cable length of the headphones connected to the Oppo 205 device, and I attempt to use another USB DAC device, the dragonfly COBOLT 1.0, it does not recognize such device and has no ability to connect to a new device in Roon Audio in the Remote Roon SW, contrary to your user manual which shows that I should be able to add or switch to a device in room audio/. Contrary to the manual, it shows no connection to a PC connected sound device such as the Dragonfly or the Laptop’s soundcard of its built in audio device, even though I know it exists on the PC and even though it works outside Roon and successfully plays sound from other PC sound sources to this DAC. My smart phone android remote Roon does successfully output to the smart phones audio device, but has limited audio capabilities and is much less robust than the PC rune software in terms of file management. I would like rune to recognize this DAC so that I can listen to my Roon files using the laptop remote Roon software which works fine otherwise.

I am an advanced PC user and very experienced using Roon, but have limited network understanding, and would be hard-pressed to access my Roon nucleus administrator access which requires that I use my Internet browser to do so and use network IP addresses, which are very complex for me with my limited network experience. Roon works very nicely in all respects except when I am supposed to do something as a network administrator, in which case I am sorry to say that your software is very user unfriendly…

Please help me fix this problem. I have already studied everything available in the user manual that I could find

Hi @Robert_Vantress,

Since you are using a Windows PC, I would verify that both Roon.exe and RAATServer.exe have been added as exceptions to your Windows firewall.

You can use these instructions to add the exceptions and the executables themselves would be located in your Database Location/Application folder path.

I would also add these exceptions to any Antivirus or other Firewall blocking applications you may have and ensure that you connected to your network via a Private network, not a Public one, see this guide for more information.

Noris, Thanks for responding. This seemed to resolve it, but I might add
that in particular, I had the network setting on public. When I switched it
to private, it worked. However, it then started causing drop outs on the
Oppo 205 Network (Roon Ready) Zone, so that on this laptop compute it loses
the zone after a small amount of playing time. The Roon software works fine
even after the sound dropped. I can exit Roon and come back in and it will
have the Oppo 205 zone, but I lose it again. I have reset all of the
network, router and Roon nuceus and Media Servers but the problem persists.
Roon works well on all other zones and remote devices. I suspect that the
Oppo205 drive may have now become a problem or there is a setting problem.
Any ideas, or do I need to start a separate Roon support topic? There is no
help from Oppo as they are out of business and their driver is no longer
supported. But since it is Roon ready, I assume you guys know about this.
Thanks for your help. Rob

Hi @Robert_Vantress,

Glad to hear that this aspect is resolved.

Is your Oppo up-to-date on the latest firmware? What does your network setup look like, can you let me know the model/manufacturer of all your networking gear?

You should also be aware that using WiFi is less reliable than using an Ethernet connection, I would try temporarily connecting both the Nucleus and the Oppo via Ethernet cable to the primary router and see if this helps.

In response to your questions, I am running a Roon Nucleus core directly cabled to the Router, a Netgear Orbi RBR40m which has one plug in extender upstairs, and has an ethernet switch linked upstairs to the office which controls one roon Remote and oppo HA 1 device which works fine. The problem is in the listening room where there is no ethernet and one Roon Ready Network 205 Blue Ray and DAC, controlled by a laptop roon remote, playing through the headphone amp which requires that the Oppo 205 stay there on the rack. The laptop can be moved around. I have ordered an Orbi extender with ethernet ports that will serve both e Oppo 205 and a portable DAC attached to the Laptop when in that Room via USB. The exting ORBA should have been plenty big enough given the size of the home. Also, the Roon remote in the smart phone and table can controol the Oppo 205 without problems, so it seems that the driver may not be the problem. However, the drive is the latest issued by Oppo before it shut down the business.

Hi @Robert_Vantress,

This should help by a bit. Also, since you’re using an Orbi setup, I’d check your IGMP settings (as mentioned in Networking Best Practices Guide):

Netgear Orbi Routers

If you’re making use of an Orbi router, we recommend unchecking Disable IGMP Proxying in your router’s settings. This setting can interfere with the ability for Roon Remotes to connect to the Roon Core.

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