Issue with Audio Devices Disappearing After Remote Wake from Sleep via WoL (ref#DTE75G)

What’s happening?

· I'm having trouble with my DAC, speakers, streamer, etc.

What best describes the issue with your audio device?

· My device used to show up in Settings > Audio, now it's gone

Describe the issue

Core Roon server is a powerful and up to date Windows 11Pro 23H2 desktop. Roon server and client software versions also kept up to date. This is a long running problem since Roon was installed on this machine. I am a lover of both a) Windows "power saving" features and b) my ability to remotely wake the Core/server machine via WoL (using either my SqueezeBox remote controls or my phone). After a few minutes without playing music the server often goes to sleep as expected. The issue is that *sometimes* (about 70% of the time) when remotely woken from sleep via WoL, Roon reports that there are no audio devices (and the devices usually listed on the "Settings">"Audio" page have disappeared). When that happens, if I attend the server in-person and log in to Windows, the devices magically reappear in Roon. Thanks

Describe your network setup

Wired network of multiple squeezeboxes

Hello @Matthew_Jobling ,

Thanks for reaching out. Can you confirm if you have set up RoonServer as per these instructions?

When you reproduce the issue, I assume you are fully shutting off the PC and not just putting it into Sleep/Hibernate mode, correct?

Hi Noris! Thanks for your reply and for endeavouring to help me. I can see from your questions that I did not describe the issue very well. Sorry about that. I was trying to describe the behaviour of the Roon music system, as viewed from any Roon client on my network (e.g. Windows or Android clients with Roon installed), when the Roon server is remotely awakened from Sleep - sometimes the audio devices are all present, and sometimes they are all not - it shows some kind of message to the effect of it searching for devices. This happens only sometimes - not every time - an intermittent issue. When the issue occurs, it is remedied by me walking over to the Roon server and physically logging in to Windows on that device - when I do so, all the audio devices magically return to the list (as viewed by any of my Roon clients)

I have not performed any configuration in the Windows OS of my Roon server for the OS to automatically login. My understanding of the way Roon Server functions is that it behaves like a service in that my Roon clients should be able to connect to the server, see the audio devices, play music etc. regardless of whether any user is logged in to the console of the server. Thanks

Hi @Matthew_Jobling,

We’ve examined diagnostic reports automatically sent to our servers in the interim period and captured what we can assume is the event you’re describing.

In this case, RoonServer is logging a forbidden access error when attempting to access a network socket. Do you have any antivirus software on this machine that might be interfering with RoonServer’s network activity when backgrounded?

I’d also double-check that the location in which you’ve installed the database (RoonServer folder) has adequate permissions on this machine.

Hi Connor. Fantastic - thank you for taking the time to look at diagnostic info for me

Interesting idea that some security software might be doing this. As I’m sure you are aware, these days there is quite a long list of security software features just included in the Windows OS in relation to such things as virus/threat/ransomware protection, firewall, app control, exploit protection etc… In addition to this I have MalwareBytes Premium and Acronis Cyber Protect Home Office installed

Regarding the latter two I could experiment with selectively disabling them (or some of their features) to see if it changes the reliability of Roon being able to access the output devices after wake-up from sleep via WoL

I’ll try to do that and will report back

Thanks

Hi @connor I’ve taken some time to disable both MalwareBytes Premium and Acronis Cyber Protect Home Office, then experiment with a few WoL tests. Unfortunately it doesn’t look like either of these two pieces of security software are causing the issue as it persisted throughout the test regardless of whether either was enabled/disabled

What do you advise?

Thanks,
Matt

Hi @Matthew_Jobling,

Thank you for your patience. The connection between RoonServer/RAATServer and all Zones (including Squeezebox, Chromecast, and others) is severed when this machine goes to sleep, and upstream requests from RoonServer to the internet subsequently encounter timeouts and network reachability failures. Upon waking, RoonServer does appear to be logging handshakes with these Zones, but it takes some time for the device announcements to filter through the network/drivers and engage with RoonServer. To the user, this would match the symptoms you’ve described.

In logs, we can see RoonServer’s other background processes fail during hibernation, as well. Roon can’t reliably reach the broader internet to check the time or ping account servers to authorize sessions.

First off, is RoonServer.exe a whitelisted process in the Windows Defender firewall?

Secondly, do you have IGMP snooping enabled in the system administration settings of your routers and managed switches? Please list any network hardware other than the main router in use with your audio ecosystem. The more detail, the more efficiently we can identify the failure point. Thanks!

What’s happening?

· Something else

How can we help?

· None of the above

Other options

· Other

Describe the issue

I wish to re-open request ref#DTE75G please - "Issue with Audio Devices Disappearing After Remote Wake from Sleep via WoL". Sorry @Connor that it took me so long to respond. I wish to re-open the dialogue and continue the investigation, please. You kindly replied to me on July 10th as follows:

"Hi [@Matthew_Jobling], Thank you for your patience. The connection between RoonServer/RAATServer and all Zones (including Squeezebox, Chromecast, and others) is severed when this machine goes to sleep, and upstream requests from RoonServer to the internet subsequently encounter timeouts and network reachability failures. Upon waking, RoonServer does appear to be logging handshakes with these Zones, but it takes some time for the device announcements to filter through the network/drivers and engage with RoonServer. To the user, this would match the symptoms you’ve described.

In logs, we can see RoonServer’s other background processes fail during hibernation, as well. Roon can’t reliably reach the broader internet to check the time or ping account servers to authorize sessions.

First off, is RoonServer.exe a whitelisted process in the Windows Defender firewall?

Secondly, do you have IGMP snooping enabled in the system administration settings of your routers and managed switches? Please list any network hardware other than the main router in use with your audio ecosystem. The more detail, the more efficiently we can identify the failure point. Thanks!"

I do not have “RoonServer.exe a whitelisted process in the Windows Defender firewall”. Please tell me how you would like for me to do this and I would be happy to configure this

There is no other network hardware involved between the wired Roon server and the wired Squeezeboxes other than the main router. No settings were changed on the main router. No settings are visibly present on the main router for IGMP or anything else multicast-related

Thank you

Describe your network setup

Wired network of multiple Squeezeboxes. Roon server is Windows 11 Pro 23H2

Hi @Matthew_Jobling,

Thanks for following up!

Here’s more info on firewall settings: https://help.roonlabs.com/portal/en/kb/articles/firewall#For_Windows_10

A simple way to test this can also be to temporarily disable your windows firewall and see if your issues persist. :+1:

Thanks Benjamin. I followed the process steps detailed at the link you kindly provided to permit the following app to communicate through the Windows 11 firewall:

C:\Users\mattj\AppData\Local\RoonServer\Application\RoonServer.exe

I’ll get back to you in the next few days and let you know whether it improved the situation or not

Great we look forward to hearing back from you!

My issue is resolved, thank you daniel, benjamin and connor

I whitelisted the RoonServer in the Windows firewall, Windows antivirus/malware and my other security tools. All players are now present immediately when the Roon server is remotely woken from sleep via WoL

Many thanks for your support and for such a great product

1 Like

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

Sorry to have to do this, but I have requested that this case be re-opened as the symptoms reappeared a couple of days after I reported they had gone

I still suspect the issue is somehow related to Windows security/authentication…

When woken remotely via WoL the Roon Remotes can connect to the server and browse the library but it is reported that no audio devices are found to actually play anything. Only when the server console is physically attended to and logged in are the players found

Thank you

Hey @Matthew_Jobling,

Thanks for writing back in! Sorry to hear your issues persist.

Could you share a more specific date and time of when you perform the above, and eventually get your audio devices re-connected?

You may be onto something here. Do you have any additional antivirus software active on the machine? Or, since you’re using the network to wake the machine up, perhaps double-checking proper firewall permissions from your router as well?

In the meantime, we’ll have our QA team attempt to reproduce this as well.

Hi Benjamin. Thanks for your support

At 09:08:58AM (Pacific Time) this morning I woke the Roon server remotely via WoL. 1 - 2 seconds later (approximately 09:09:00AM) I was able to see the server wake - I was able to tell that the server was awake from a) the LEDs on the server chassis as well as b) I could see the Roon client connect to the server (library browsable but “no audio devices found” - exactly like the screenshot I shared)

About a minute later, at 09:10:00AM (Pacific Time), with the system still in the state described above, I pressed a physical key on the server console to initiate Windows Hello sign-in. Almost immediately after doing so (within about a second of doing that), the audio devices had become visible on the client, so I was able to enjoy some music

I think we’ve already gone through thinking about whether the security tools are causing the issue but you did ask the question:
I have the standard Windows 11 client software firewall, with both MalwareBytes and Acronis Cyber Protect Home Office Essentials for anti-malware/anti-virus

Thank you

Sorry not to have stated the date! This was Sunday: 22/09/2024