# Remote unable to connect to Roon server after software updates (ref#E5GL6C) **URL:** \ **Category:** Support\ **Tags:** rctt\_null-02-1\ **Created:** [June 11, 2026, 11:00pm UTC](https://community.roonlabs.com/t/remote-unable-to-connect-to-roon-server-after-software-updates-ref-e5gl6c/321503 "2026-06-11T23:00:40Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![thotdoc](https://community.roonlabs.com/user_avatar/community.roonlabs.com/thotdoc/32/46484_2.png) [@thotdoc](https://community.roonlabs.com/u/thotdoc)\ **Post date:** [June 11, 2026, 11:00pm UTC](https://community.roonlabs.com/t/remote-unable-to-connect-to-roon-server-after-software-updates-ref-e5gl6c/321503/1 "2026-06-11T23:00:41Z")
#### Hi! What’s not quite right with Roon? · Can’t reach my Server, remotes or ARC #### Can’t connect to my Server, remotes or ARC · Other ARC issues #### Tell us what's going on · I've upgraded Roon to latest version and Sonic orbiter to a late version...V2.8. My computer that holds Roon can communicate with the SonicTransport as I've used the computer to download new System software for the Transport. So all components are working and can communicate. But the computer as remote will not connect with Roon server. #### Tell us about your home network · No VPN. Switch is an old Cisco Catalyst 2960G. Extenders are Ubiquiti that have a history of working in this system ---
**Author:** ![thotdoc](https://community.roonlabs.com/user_avatar/community.roonlabs.com/thotdoc/32/46484_2.png) [@thotdoc](https://community.roonlabs.com/u/thotdoc)\ **Post date:** [June 11, 2026, 11:29pm UTC](https://community.roonlabs.com/t/remote-unable-to-connect-to-roon-server-after-software-updates-ref-e5gl6c/321503/2 "2026-06-11T23:29:55Z")
I imagine this is the problem. But I do not know how to “fix” it. I went to [sonicorbiter.com](http://sonicorbiter.com) and this came up. **"Music Servers 0** No Sonicorbiter OS based music servers found on your network. **Note:** Your music server will not show up here unless it’s running Sonicorbiter OS #### **Network players 0** No Sonicorbiter OS based music players found on your network. **Note:** Your music player will not show up here unless it’s running Sonicorbiter OS" That doesn’t make sense as the Sonic Transport was ‘here’ when I installed the newest version of SonicOrbiter on it this afternoon. ---
**Author:** ![benjamin](https://community.roonlabs.com/user_avatar/community.roonlabs.com/benjamin/32/348120_2.png) [@benjamin](https://community.roonlabs.com/u/benjamin)\ **Post date:** [June 11, 2026, 11:41pm UTC](https://community.roonlabs.com/t/remote-unable-to-connect-to-roon-server-after-software-updates-ref-e5gl6c/321503/3 "2026-06-11T23:41:25Z")
Hey @thotdoc, Thanks for the report and additional findings! Roon discovery and the > **[MySonicorbiter](http://sonicorbiter.com)** “find devices” page both rely on multicast/mDNS broadcast traffic staying on the same subnet. The fact that the computer can pull OS updates but _neither_ Roon nor > **[MySonicorbiter](http://sonicorbiter.com)** can discover the Transporter tells you unicast routing works but multicast/broadcast discovery is being blocked or split. That points squarely at the network layer, not at Roon or SonicOrbiter. The most likely culprits, in order: 1. **Devices on different subnets / VLANs.** If the upgrade or a reboot caused the Transporter and the computer to land on different subnets (e.g., one on the main LAN, one behind a Ubiquiti extender acting as a separate network), discovery dies. This is the single most common cause. Confirm both devices have IPs in the same range (e.g., both 192.168.1.x). 2. **Ubiquiti extender in a mode that isolates clients.** Some Ubiquiti extender/AP modes block client-to-client and multicast traffic ("client isolation" or operating as a router rather than a bridge). Even with a history of working, a firmware update can flip behavior. 3. **IGMP snooping / multicast filtering on the Cisco Catalyst 2960G.** This switch has IGMP snooping enabled by default, and if there's no IGMP querier on the network, multicast (including mDNS) can get dropped after a topology change. First, find both IP addresses. On the SonicTransporter, go to its web admin (sonicorbiter setup page) and note its IP. Then check the computer’s IP. If the first three octets don’t match, that’s the problem, they’re on different networks. Second, eliminate the extenders as a variable: temporarily plug the computer directly into the same Cisco switch the Transporter is on, via Ethernet, and check whether Roon and > **[MySonicorbiter](http://sonicorbiter.com)** now find it. If it works wired-direct, the Ubiquiti extenders are isolating traffic. Third, reboot in the right order: power down the Transporter, reboot the switch, then power the Transporter back up, then the computer. After a firmware change, IGMP snooping state on the 2960G can get stale, and a clean switch reboot often restores multicast forwarding. Fourth, if it only works when wired-direct, the fix lives in the Ubiquiti config, ensure the extenders are bridging (not routing/NAT) and that any client/guest isolation is off. We’ll be monitoring for your reply and results, thank you! 🙏 ---
**Author:** ![thotdoc](https://community.roonlabs.com/user_avatar/community.roonlabs.com/thotdoc/32/46484_2.png) [@thotdoc](https://community.roonlabs.com/u/thotdoc)\ **Post date:** [June 13, 2026, 11:32pm UTC](https://community.roonlabs.com/t/remote-unable-to-connect-to-roon-server-after-software-updates-ref-e5gl6c/321503/4 "2026-06-13T23:32:39Z")
1. The router and the transport are on the same network: Router-192.168.0.1 Transport-192.168.0.30 1. Plugging the computer directly Inyo the switch did not all me to find the Roon Server 2. I powered down and up in the correct order 3. I deleted my VPN account Still unable to get to the Roon server More ideas? Thank you ---
**Author:** ![vadim](https://community.roonlabs.com/user_avatar/community.roonlabs.com/vadim/32/335515_2.png) [@vadim](https://community.roonlabs.com/u/vadim)\ **Post date:** [June 18, 2026, 6:54am UTC](https://community.roonlabs.com/t/remote-unable-to-connect-to-roon-server-after-software-updates-ref-e5gl6c/321503/5 "2026-06-18T06:54:04Z")
Hi @thotdoc, Thanks for trying those steps. Based on your account diagnostics, we can see that your SonicTransporter is running a very old Linux kernel (Fedora 25 core), and Roon 2.65 introduced new system requirements: **glibc 2.27 or later** on Linux. Your unit appears to pre-date that threshold, which is most likely why RoonServer stopped working during the update. This isn’t something that can be resolved from the Roon side - the underlying OS on the SonicTransporter needs to be updated to meet the new requirements. We’d recommend reaching out to **Small Green Computer** (the makers of SonicTransporter) directly and asking them to update your unit’s OS to a version that meets the 2.65+ requirements. You can find more details about the system requirements change in the [Roon 2.65 release notes](https://community.roonlabs.com/t/roon-2-65-and-arc-1-77-are-live/318732). ---
**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:** [June 23, 2026, 2:44pm UTC](https://community.roonlabs.com/t/remote-unable-to-connect-to-roon-server-after-software-updates-ref-e5gl6c/321503/7 "2026-06-23T14:44:19Z")
---
**Author:** ![thotdoc](https://community.roonlabs.com/user_avatar/community.roonlabs.com/thotdoc/32/46484_2.png) [@thotdoc](https://community.roonlabs.com/u/thotdoc)\ **Post date:** [July 4, 2026, 10:53pm UTC](https://community.roonlabs.com/t/remote-unable-to-connect-to-roon-server-after-software-updates-ref-e5gl6c/321503/8 "2026-07-04T22:53:32Z")
Work done to establish the repeaters were not the problem in the lack of connection. > [@Ubiquiti](#): > > As you confirm that it is running on the SonicTransport, and from the support file, I can see that the device mac is 00:30:18:50:1f:39 > > I checked your network’s support file, and everything looks perfect. Your Mac and the Sonic Transport server are on the same network and can fully see each other. > > Because this connection issue started right after the server’s v2.8 update and your UniFi settings haven’t changed at all, this isn’t a UniFi Gateway issue. The update on the music server likely changed a local sharing or security setting on the device itself. > > I highly recommend reaching out to Sonic Transport support next. Let them know that your router settings haven’t changed and both devices are on the same local network, so they can help check if the v2.8 update altered how the server shares music on the local network! (This is not likely the issue) **Work I’ve done** - Reinstalled Roon on Sonic Transport, Re-enabled the player, not able to find Storage Settings to reconfigure - Reinstalled Roon on Remote - Upgraded SonicOrbiter to V2.8 - Server and Remote on same 3-octets - So wifi allows the devices to talk to each other but still no connection between Remote and Server - Connecting Remote directly to Cisco Switch that connects directly to Sonic Transport does not allow the Remote to find the Remote to find Roon Server… ---
**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:** [July 4, 2026, 11:10pm UTC](https://community.roonlabs.com/t/remote-unable-to-connect-to-roon-server-after-software-updates-ref-e5gl6c/321503/9 "2026-07-04T23:10:11Z")
---
**Author:** ![vadim](https://community.roonlabs.com/user_avatar/community.roonlabs.com/vadim/32/335515_2.png) [@vadim](https://community.roonlabs.com/u/vadim)\ **Post date:** [July 7, 2026, 11:02am UTC](https://community.roonlabs.com/t/remote-unable-to-connect-to-roon-server-after-software-updates-ref-e5gl6c/321503/10 "2026-07-07T11:02:14Z")
Hello @thotdoc, Thank you for the systematic testing - the results are actually very telling. With the extenders ruled out, both devices confirmed on the same subnet, and discovery still failing even when the remote is wired directly into the Cisco switch, the evidence now points at the switch itself rather than at SonicOrbiter or your UniFi gear. Here’s why: unicast traffic (OS updates, web pages) passes through the switch fine, but Roon’s server discovery and the [sonicorbiter.com](http://sonicorbiter.com) “find devices” page both rely on multicast - and the Catalyst 2960G has IGMP snooping enabled by default. Without an IGMP querier on the network (home routers typically don’t provide one), the switch’s multicast tables expire over time and it silently starts dropping exactly this kind of traffic. That would also explain why both discovery mechanisms show zero devices while everything else works. Roon has no fallback here - remotes can only find the server through discovery, so when multicast is blocked, the connection is simply impossible. Three ways to address it, in order of effort: 1. Reboot the Cisco switch - this clears the stale snooping state and usually restores discovery temporarily. If discovery comes back after a switch reboot and degrades again later, that confirms the diagnosis on its own. 2. Temporarily connect the remote computer and the SonicTransporter through a simple unmanaged switch, bypassing the 2960G - unmanaged switches forward multicast without any snooping logic. If discovery works there, we have our answer. 3. For a permanent fix while keeping the Catalyst: via console access, either disable snooping globally (`no ip igmp snooping`) or enable the querier (`ip igmp snooping querier`). Please let us know the result of step 1 or 2 - that will tell us definitively where we stand. ---
**Author:** ![thotdoc](https://community.roonlabs.com/user_avatar/community.roonlabs.com/thotdoc/32/46484_2.png) [@thotdoc](https://community.roonlabs.com/u/thotdoc)\ **Post date:** [July 7, 2026, 9:59pm UTC](https://community.roonlabs.com/t/remote-unable-to-connect-to-roon-server-after-software-updates-ref-e5gl6c/321503/11 "2026-07-07T21:59:30Z")
I bought a new basic Netgear unmanaged switch and changed over all the cables…remote still unable to reach the core in the sonic transport. In your description you mentioned that neither the Transport nor the Rendu could be found. I tracked that down. I was using Safari and the sonic orb/sonic transport s could not be found because the sonic [orbiter.com](http://orbiter.com) site is not secure. I forced Safari to use it but it was hit or miss. I switched to Chrome and it works with insecure sites. I’m using Chrome and contacting the site and the two objects (orbiter and Rendu) with no problems. It is amazing to me that I can install software upgrades on the objects but can’t contact the software that allows my remote to reach the Roon core. ---
**Author:** ![thotdoc](https://community.roonlabs.com/user_avatar/community.roonlabs.com/thotdoc/32/46484_2.png) [@thotdoc](https://community.roonlabs.com/u/thotdoc)\ **Post date:** [July 7, 2026, 10:25pm UTC](https://community.roonlabs.com/t/remote-unable-to-connect-to-roon-server-after-software-updates-ref-e5gl6c/321503/12 "2026-07-07T22:25:37Z")
Ok. I connected the remote, a Mac Air with Tahoe to the switch and it didn’t connect as noted. Then I thought about it to see if the firewire bridge was working. The Mac says the firewire bridge is inactive. Then when looking for help the help says you can’t use the bridge to connect to a wifi device. So I can’t connect the remote directly to the sonic transport system using a simple switch…or any switch as you suggested or as I read it. I tried rebooting the Cisco and it did not connect ---
**Author:** ![thotdoc](https://community.roonlabs.com/user_avatar/community.roonlabs.com/thotdoc/32/46484_2.png) [@thotdoc](https://community.roonlabs.com/u/thotdoc)\ **Post date:** [July 7, 2026, 10:43pm UTC](https://community.roonlabs.com/t/remote-unable-to-connect-to-roon-server-after-software-updates-ref-e5gl6c/321503/13 "2026-07-07T22:43:26Z")
Got it to work. Thank you for your help…now I have to set up Roon. It was asking me to choose another core and I’d lose my library. I tried it anyway and it made the connection…so many hours of wasted time. Still thanks for your help ---
**Author:** ![vadim](https://community.roonlabs.com/user_avatar/community.roonlabs.com/vadim/32/335515_2.png) [@vadim](https://community.roonlabs.com/u/vadim)\ **Post date:** [July 8, 2026, 12:27pm UTC](https://community.roonlabs.com/t/remote-unable-to-connect-to-roon-server-after-software-updates-ref-e5gl6c/321503/14 "2026-07-08T12:27:32Z")
Hello @thotdoc Glad it’s finally connecting; that was a lot of hours to burn on what turned out to be a network issue. Enjoy your music! ---
**Author:** ![vadim](https://community.roonlabs.com/user_avatar/community.roonlabs.com/vadim/32/335515_2.png) [@vadim](https://community.roonlabs.com/u/vadim)\ **Post date:** [July 8, 2026, 12:27pm UTC](https://community.roonlabs.com/t/remote-unable-to-connect-to-roon-server-after-software-updates-ref-e5gl6c/321503/15 "2026-07-08T12:27:35Z")