# Roon AirPlay playback issue with Sonos speakers on separate VLAN (ref#0JBI65) **URL:** \ **Category:** Early Access\ **Created:** [October 20, 2026, 11:35am UTC](https://community.roonlabs.com/t/roon-airplay-playback-issue-with-sonos-speakers-on-separate-vlan-ref-0jbi65/326326 "2026-10-20T11:35:02Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Mark\_Walpole](https://community.roonlabs.com/letter_avatar/mark_walpole/32/5_5575768a8748004e209b776fc1b2916d.png) [@Mark\_Walpole](https://community.roonlabs.com/u/Mark_Walpole)\ **Post date:** [October 20, 2026, 11:35am UTC](https://community.roonlabs.com/t/roon-airplay-playback-issue-with-sonos-speakers-on-separate-vlan-ref-0jbi65/326326/1 "2026-10-20T11:35:03Z")
#### What best describes your playback issue? · Music doesn't start when I press "Play" #### What type of Zone is affected by this problem? · \*Network Zones\* are affected. #### Is the affected network Zone connected with Ethernet or WiFi? · WiFi #### Does the issue affect all file formats? · The issue affects \*multiple/all\* file formats. #### Does the issue happen with local library music, streaming service music, or both? · \*Both streaming and local\* \*library\* music are affected. #### Do you encounter any playback errors with the "System Output" Zone? · The System Output has \*no problem\*, it's only my other Zone. #### How is the affected Zone connected to your RoonServer machine? · Network - WiFi #### Which network audio protocol is the Zone using with Roon? · Airplay #### Since this is an Airplay Zone, have you tried toggling Airplay Compatibility Mode for this Zone in the Device Setup window? · There is no change in behavior. #### Does the device show up at all in Roon Settings -\> Audio? · The Zone is listed under the wrong protocol #### 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 #### If the device has multiple output options, do the other options work as expected? · Multiple output types are affected #### Is the device using the latest firmware as per the manufacturer? · Firmware is up-to-date but the issue remains #### Do you have an approximate timestamp of when the issue last occurred? · 20 October 2026, 14:45 Dubai time (10:45 UTC), playing "Rapture" by Blondie to Study - Sonos Five. Same failure earlier at 14:29. #### What are the make and model of the affected audio device(s) and the connection type? · Sonos Play:5 (Gen 2), 2 x Sonos Move and Sonos ARC. All are on WiFi and connect to Roon via Airplay 2. Majority of testing on Play:5. ## Describe the issue My Sonos speakers are on a separate IoT VLAN (192.168.83.0/24) and my Nucleus is on the main network (192.168.75.145). The UniFi gateway at 192.168.75.1 relays mDNS between them, and the firewall allows all traffic between the Nucleus and the IoT network in both directions. Roon Server was updated today. Roon finds the Sonos as AirPlay devices at their correct IPs, but nothing plays. The track sits at 0:00. AirPlay from my iPhone to the same speaker works, Roon plays fine over AirPlay to my B&O on the main network, and System Output on my Mac works. Compatibility Mode on or off makes no difference. From the log for the Play:5 at 192.168.83.196, pairing goes through and then: [airplay/clientV2] [192.168.83.196] Sending SETUP #1 (session) Got exception connecting to device at 192.168.75.1,7101: System.Net.Sockets.SocketException (111): Connection refused RECORD failed: 500 Internal Server Error, attempting pairing pair-verify failed: 400 Bad Request, trying airplay1 fallback for shairport-sync So Roon pairs with the speaker on its real IP, then tries the next connection on the gateway's IP instead. My Samsung TV on another subnet shows the same thing in the log (IPEndPoint=192.168.75.1:7000, when it's really at 192.168.79.64). It looks like Roon is using the address of the relayed mDNS packet rather than the device's own IP. Happy to send full logs. ## Describe your network setup UniFi Dream Machine SE as router, with UniFi switches and UniFi APs. Nucleus wired by Ethernet on the main network (192.168.75.0/24). Sonos speakers on Wi-Fi on a separate IoT VLAN (192.168.83.0/24). The UDM's built-in mDNS proxy relays discovery between the two. Firewall rules allow all traffic between the Nucleus and the IoT VLAN. No range extenders or mesh. All APs are wired back to the Dream Machine SE. ![](https://api.typeform.com/responses/files/f477889edf9586b3f18ec014d8040e7525f4c9a85d5913c4e7e3cc543a6e830c/Screenshot_2026_10_20_at_15.33.48.png) ---
**Author:** ![mjw](https://community.roonlabs.com/user_avatar/community.roonlabs.com/mjw/32/382057_2.png) [@mjw](https://community.roonlabs.com/u/mjw)\ **Post date:** [October 20, 2026, 12:45pm UTC](https://community.roonlabs.com/t/roon-airplay-playback-issue-with-sonos-speakers-on-separate-vlan-ref-0jbi65/326326/2 "2026-10-20T12:45:49Z")
Please note that Roon does not officially support VLANs (since device discovery doesn’t work.) This is what Roon says on the matter. > **[FAQ: Adding Roon as a Firewall Exception](https://help.roonlabs.com/portal/en/kb/articles/firewall)** > > Symptom Summary If Roon Server or Roon Remote can't see other devices, zones, or your Roon Server on the network, a firewall or antivirus software may be blocking Roon's network access. This guide will walk you through checking your firewall settings... However, some do use VLANs, so head over to the #Tinkering category for help setting this up. ---
**Author:** ![connor](https://community.roonlabs.com/user_avatar/community.roonlabs.com/connor/32/172788_2.png) [@connor](https://community.roonlabs.com/u/connor)\ **Post date:** [October 20, 2026, 6:45pm UTC](https://community.roonlabs.com/t/roon-airplay-playback-issue-with-sonos-speakers-on-separate-vlan-ref-0jbi65/326326/3 "2026-10-20T18:45:28Z")
Hi @Mark_Walpole, Does this same problem reproduce if you put these Airplay endpoints on the same subnet? Test with a single endpoint and then expand from there. Since you’re on Early Access, we’re going to migrate this for visibility to the appropriate teams. ---
**Author:** ![Mark\_Walpole](https://community.roonlabs.com/letter_avatar/mark_walpole/32/5_5575768a8748004e209b776fc1b2916d.png) [@Mark\_Walpole](https://community.roonlabs.com/u/Mark_Walpole)\ **Post date:** [October 21, 2026, 9:12am UTC](https://community.roonlabs.com/t/roon-airplay-playback-issue-with-sonos-speakers-on-separate-vlan-ref-0jbi65/326326/4 "2026-10-21T09:12:30Z")
Hi @connor Tried it. Plugged the Play:5 in with a cable on my main lan (same subnet as the Nucleus) and Roon played to it first time. Took the cable out so it went back on wifi on the IoT vlan and it failed again, exactly like before. What I can see in the log is it pairs ok with the speaker on 192.168.83.196, but the next connection goes to 192.168.75.1:7101. Thats my UDM, not the speaker, so it just gets refused and then RECORD failed: 500. The UDM is running the mDNS proxy so I think Roon is picking up the address of the proxy rather than the speaker. AirPlay from my phone works fine to them on either network so it does seem to be a Roon thing. Can send more logs or try an early access build, whatever helps. Mark ---
**Author:** ![system](https://roon-community-uploads.s3.amazonaws.com/original/3X/d/e/deefbd9083c99c82bbf2dd3f873f52a49f5db881.png) [@system](https://community.roonlabs.com/u/system)\ **Post date:** [October 28, 2026, 9:13am UTC](https://community.roonlabs.com/t/roon-airplay-playback-issue-with-sonos-speakers-on-separate-vlan-ref-0jbi65/326326/5 "2026-10-28T09:13:26Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.