Sounds like you added to new Deco WiFi to your existing (wired) network. If so, please make sure the Deco is set to Access Point Mode and not to Router Mode. As it sounds from your description right now, your Deco is set to Router Mode (default) and thus creating it’s own independent network but for Roon, all the devices have to be in the same network. The fgfollowing article may provide guidance for checking/changing settings on your Deco:
That is interesting, however I have just replaced an older Orbi mesh network running in router mode and that always worked fine. I like running in router mode as the Deco offers additional services not available in Access point mode (as explained in the link you sent). All my other IoT devices are working fine, and to redo the network to access mode is not an attractive option.
I have always set my private IP address and subnet on my router not the cable modem.
So, I am looking for others to confirm or I will have to drop Roon, at least until is overcomes this issue.
Thanks for your response
@Charles_booth, are your wired Roon clients connected directly to the BE11000 (and thereby being on the same subnet as the WiFi clients)? Does your BE11000 provide DHCP to each of its clients? Does your cable modem also act as a router or just as a modem?
Sorry but we have to go by what you tel us, which is not much, and try to anticipate the rest – which sometimes works better than on other times. So if my shots in the blue have missed the target then please follow Robert_F’s advice and provide more information about your current network setup, configuration and relevant devices. Also check Roon’s documentation (just in case);
My wired clients and roon server are connected to a gigabit switch that is connected to the deco router. The router is connected to the cable modem. I interface with the deco router to set the LAN address and subnet. My android phone via wifi can connect to the router, but cannot find Roon server running on my PC (win 10 pro).
Furthermore, when opening Roon on the PC, I see that it is running Roon version 2.0 (build 1455) although the change log does not refer to builds, but as Roon 2.0.40 being the latest without mention of build number. Also Roon bridge is version 1.7 and will not update (“There was an error checking for an update”) if that sheds any light on the topic.
Furthermore, I can ping the local ip address of my pc (roon host) from my phone.
I have two routers in my network, one gateway from my AT&T which is required for their fiber service and my own ASUS mesh network which I use for everything on my home network. I set the subnet on my ASUS router, set the ASUS for DNS and DHCP, and deactivated WiFi on the AT&T gateway, so everything is being served by my ASUS mesh network for both wired and wireless clients, all using the single ASUS subnet. My Roon Server PC is hardwired to the primary ASUS router.
I believe @BlackJack and I are still a bit unclear why your mobile devices are not seeing Roon if they are all on the same subnet.
You should probably check your new router’s settings for anything hat might affect multicast. Use the “Networking Best Practice” guide I linked as a hint for such settings.
Note: All your working wired devices are, by your description, connected to the same switch – so their communication does not go through the router. All your non working devices are wireless, which means their communication has to go through the router.
Please consider contacting the manufacturer’s support team too. It might be a device specific issue (firmware) or a misconfiguration of some sort.
We’ve activated diagnostics for your RoonServer machine to inspect logging more closely. Logs show repeated sample dropouts and timeouts when RoonServer is attempting to download and distribute audio to your endpoints, including wired Roon instances and Zones.
Based on your description of the network topology, multicast routing problems might be present as a result of a) the switch (if it has traffic management capabilities) or b) the specific settings applied to the mesh network.
This particular router setup, the BE11000, is tri-band - try restricting the network to a single band temporarily as a test.
Please elaborate on the specific implementation of your switch or consider bypassing it entirely for troubleshooting. In the mesh network settings, verify that multicast forwarding is enabled. IGMP snooping isn’t technically required for Roon, since Roon functions on a single VLAN only, but in certain router implementations, IGMP snooping will prohibit all multicast passage when deactivated. So, activate it for now if available.
Hi Conner:
Here is more information to help.
I have not been able to connect via phone since replacing a Netgear Orbi mesh system that had failed. The new Deco has the fewest options for configuring that I have seen.
ET2251 Modem provides the gateway, via a single wired connection to the Deco BE11000 (Costco version) router. From the deco router is a connection to a switch (TPlink TL-SG116 gigabit switch), and through the switch the Roon server is connected via Ethernet.
The cable modem is located on a completely different ip address and subnet than that I have programed into the Deco router/Wifi for the LAN. I have verified that Roon server, phone, wired devices, wifi devices are all on the same LAN and subnet as the roon server. Phone can ping the roon server PC. MLO network is disabled.
The DECO router has three nodes and uses Ethernet connections between the nodes for the backhaul.
The roon server (Win 10 pro PC) has a wired connection. It contains my library.
My prefered remote device is my Samsung Galaxy S21 5G. and using the “manage router” on the phone settings manager connects to the Deco router confirming it is the operating router at 192.168.xxx.1 that serves the phone its DHCP address. I have verified that the phone can ping the Roon server PC over the LAN.
A Ping&Net app on the phone reports that the Deco router is the wifi LAN gateway.
The PC (roon server) also confirms that that Deco is the operating router.
All devices connect through the switch (TPlink TL-SG116 gigabit switch) which is connected to the TPlink DECO BE11000 router. Only the to-link DECO BE11000 is connected to the gateway. I have never accessed the switch options as it claims to self configure, and it has always worked.
There are no notes on TPLink or deco routers in “Router Specific Settings” section of Best Practices.
There is no mention in the router manual or app of “multicast”. There is an option for WAN unicast, but that is not enabled.
There is no option for restricting to single band.
IPSTV/VLAN is disabled
Static routing is disabled
QoS is disabled.
Router firmware up to date.
No reference to IGMP found in the app for the router.
A Samsung SM-T510 tablet on WiFi also cannot connect to the Roon server and IP indicates it is on the same LAN.
On the Roon server, firewall exceptions are made for Roon,Roonappliance, and RAATserver, both public and private.
Here is what is displayed on the BE11000 router (xx for obfuscation) when addressing it over LAN ethernet
Internet Status: Online
Internet Connection Type:
Dynamic IP
IP Address: 76.aaa.bbb.ccc
Subnet Mask: 255.255.240.0
Default Gateway: 76.ddd.eee.fff
Primary DNS: 209.18.47.61
Secondary DNS:209.18.47.63
LAN
MAC Address: 74-FE-CE-82-xx-xx
IP Address: 192.168.xxx.1
Subnet Mask: 255.255.255.0
There is no need to obfuscate non-routeable private IP addresses and knowing their details may allow helpers to help you (quicker/better) – but you should have obfuscated your public IP address (so as not to provoke potential incidents), can’t think of a reason any helper needs that specific address in full detail.
PS: Obfuscating usually happens after the last dot in the address.
I also still think that you should contact TP-Link product support for your new DECO router. Discuss the issue with them, mention the multicast problem you seem to face, and see how they can help you.
As a side note - I notice that you may be running some older, outdated versions of the Roon app on your mobile devices.
An easy way to update them in your case would be to fully remove the app from your device and perform a fresh install of the Roon app from your app store.
Let me know if you continue to run into issues while running the latest version of Roon across your remote devices.
I seem to have stumbled into a solution! In checking (one more time) I noticed that one of the firewall permissions for the PC running roon server did not have the private and public exceptions for roonappliance.exe checked. I have no memory of altering these settings, but somehow this was changed. The Deco works fine and is in router mode.
Thus, the system is working, and I can play music! To Blackjack, Robert, Benjamin, Connor, thanks for your suggestions.
Rocky
(Windows) Updates sometimes change settings without notification. With the firewall on the server blocking access, all your clients. wired and wireless, should have been blocked. So there is still a mystery.
