Local PC Speakers Disappeared from Audio Zones After NAS IP Change
Setup
Roon Core: Running on UGreen NAS
Roon Client: Windows 10 PC
Issue: Local PC speakers (system output) no longer appear as an available audio zone
What Happened
Everything was working fine until recently. The only change that occurred was the IP address of my UGreen NAS (which hosts the Roon Core) changed on my network.
Current Situation
The Roon client on my Windows 10 PC successfully connects to the Core on the NAS
In Settings → Audio, I only see one device: my external DAC/decoder
The local PC speakers/system output zone has completely disappeared
The PC speakers work fine with other applications (tested and confirmed)
I used to be able to play music through the local PC speakers as a private zone
What I’ve Already Tried
Restarted the Roon client multiple times
Reinstalled Roon Client
Restarted the Windows 10 PC
Verified that PC speakers are set as default audio device in Windows
Checked that the speakers are not disabled in Windows sound settings
Confirmed the Roon client is properly connected to the Core
Question
How can I make the local PC speakers reappear as an available audio zone in Roon? Is there a setting I need to re-enable after the Core’s IP address changed? Do I need to reset something in the client configuration?
Could be your firewall on the PC, the server has to get a response from your PC when it queries your PC as to installed audio devices. Firewalls can block this, as can the network PC being set to private, as can the NAS and PC being on two separate subnets.
So, I’d guess
Check to make sure the PC and NAS are on the same subnet
Verify that the PC doesn’t have the network set to Public, if so, set it to private.
Check the firewall, turn it off on the PC to test, does Roon now see the PC’s audio? In either case turn on the firewall again. If the PC’s audio was seen then that means you need to allow the appropriate Roon packages, Roon, Roonserver, raatserver.
Thank you for the suggestions! I’ve tested everything you recommended, but unfortunately the issue persists:
1. Subnet Check ✓
Verified that both the PC and NAS are on the same subnet (192.168.x.x)
Both devices have the same subnet mask
They can communicate with each other properly
2. Network Profile ✓
Confirmed the PC network is set to Private (not Public)
Changed it to Private just to be sure and restarted Roon
3. Firewall Test ✓
Temporarily disabled Windows Defender Firewall completely
Restarted Roon client
The local PC speakers still do not appear
Re-enabled the firewall immediately after testing
4. Firewall Rules ✓
Even though disabling the firewall didn’t help, I added firewall rules anyway for:
Roon.exe
RoonAppliance.exe
RAATServer.exe
Allowed both Private and Public networks for each
Result: Despite all these tests, the local PC audio output zone still does not appear in Roon. The client connects to the Core perfectly fine, I can see my external DAC, but the system output/PC speakers remain invisible.
Any other ideas on what could be blocking the local audio zone detection?
How are you running Roon on that NAS? Only QNAP and Synology as far as I know, and, that was through a 3rd party to maintain.
If your answer is Docker, then be aware that Roon does not support running the software in containers. I can move this post to the Tinkering section, where someone who does use Docker containers may be able to provide an answer. Let me know.
Yes, I’m running Roon Core via Docker on the UGreen NAS. I understand it’s not officially supported, but this setup has been working flawlessly for over a year until the NAS IP address changed.
The Docker container is still running fine - the Roon client connects to the Core without issues, I can browse my library, and my external DAC shows up in the audio zones. The only thing that disappeared is the local PC speakers zone after the IP change.
If you think this belongs in the Tinkering section where Docker users might have insights on network configuration issues, please feel free to move the thread there.
