Custom PC with AMD Ryzen Threadripper 3960X CPU, 64GB RAM, multiple SSD and mechanical internal drives, Windows 10 Pro 2020H2 build 19042.630. Connected to router with 1Gb ethernet.
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Asus RT-AX88U router; Chromecast and Android devices connected via WiFi
2 Google Chromecast devices connected to LG soundbars, one LG soundbar with Chromecast built in, 2 Android 8 and 1 Android 10 remote devices.
Description Of Issue
Earlier today I switched an existing Asus TM-AC1900 router for a new Asus RT88XU router. Nothing else changed. I turned down all network devices first (and shut down Roon), turned off the AC1900, connected the RT88XU, configured it to use EXACTLY the same 2.4Ghz and 5Ghz SSIDs and passwords as the AC1900, and then starting allowing clients to reconnect, all of which did so with no issue including fiddly “smart” devices that frequently have problems with changes like this. No software on the Roon Core PC was changed. There weren’t any Windows updates applied. Now, when I launch Roon, all the Chromecast devices (and groups) and Android remotes that were working with it are no where to be found, and none of the Android remote devices can connect to Roon on the PC. I’ve double- and triple-checked settings on the new router (it has nearly an identical UI to the previous router and the configurations are very similar as well)–nothing is being blocked. I checked Windows Firewall: raat.server and Roon.Exe have permissions just as they always have. Multiple PC restarts have not helped. By forcing the Roon Android app to quit and clearing the cache on the device, I can sometimes get an Android remote to show up fleetingly in Roon’s list of audio outputs, but even then the Android device can’t connect to Roon. Google Home can see all the Chromecast devices on the LAN. They all show up in the router’s list of connected clients. I can direct audio via Chromecast from an Android device to any of the Chromecast devices, so there’s nothing blocking that protocol on the LAN. I’ve looked at the Roon logs but frankly they’re so dense and prolix that it’s nearly impossible to find any information in them without whatever secret decoder ring must be necessary. So I have nothing else to try except to remove Roon entirely and reinstall? Which I would do if I had any confidence it would help, but I’m not sure it will. Your input would be helpful. Happy to send log files upon request.
Not sure to be honest, I have struggled in the past with an Android phone. I currently use an ASUS RT AC86U on stock firmware IGMP snooping is enabled under wifi and Multicast Routing is enabled under LAN IPTV . Currently both Chromecasts and the Android phone are identified and enabled by Roon. I do recall on one occassion having to insert the IP address for core ( under help) when the android remote couldn’t connect.
We recommend enabling “Enable Multicast Routing” option in settings.
Hi @Axel_Lesch Did this. Ripped out my entire Google Home setup including every last device. I reinitialized the LG soundbars with built-in Chromecast and rejoined them to the LAN. I reinitialized two Chromecast devices and also rejoined them to the LAN. All the devices have different names. I removed the wifi configuration on all the Android devices and then rejoined them. I removed Roon entirely from all of those devices in the interim and then reinstalled on just one device. None of this has had any impact. Roon continues to see 0 Chromecast devices, and the Android tablet that I just reinstalled Roon upon can not communicate with the Roon Core on my PC. Router reboots and PC restarts haven’t helped. So I continue to have a Roon installation that can’t interact with anything on my network. Other audio applications (Media Monkey, Tidal) can cast (from the same devices that can’t talk to Roon) to the same devices that Roon can’t even see, so this is looking to me more like a Roon-specific problem.
Sorry it didn’t work, the other WiFi setting I have disabled is under ‘wifi professional’ is ‘Airtime Fairness’ . This was set as a recommendation from snb forums as a 'basic setting for reliability and a google shows possible advantage with it disabled for chromecast devices. However I agree if they work on Tidal why aren’t they working on Roon
Post #4 different router but I believe still applies
O well @Robert_Lowe, one last idea …
The Asus router is connected to a modem, right?
How is that configured?
Is the modem in bridge mode with NAT and DHCP disabled?
If not, double NAT could be the culprit. Anything that automatically opens ports like UPNP will fail, because the “outside” NAT can’t be accessed. @support should be able to answer exactly how this works with Roon.
One last question - the Core PC is connected to the Asus router and not to the modem and Roon is configured as an exception in the PC’s firewall?
… if none of this applies, I have no clue anymore (except maybe to factory reset the Asus)
Hi @Axel_Lesch The router is connected to a Surfboard cable modem that has no user configurable options. It is in exactly the same state as it has always been. The Core PC is connected to the Asus router. As mentioned, both roon.exe and raat.server are allowed in Windows firewall for both “public” and “private” networks, which is the configuration that I’ve always had. And with due respect, I’m hard-pressed to see why a change of router would require enormous painstaking efforts at tweaking every possible setting to get a solution that is sold as broadly functional to work. If Roon can only work on specific devices with specific configurations, then where’s the list of the devices and configurations? I’m not averse to a certain amount of device management but if you ship software that only works on X routers configured in X manner, then publish that (and this does not qualify) or get your product off the market. Or respond to user requests for help. No one from Roon has appeared on this post.
if you still want to try something last - maybe the old router was set up as an acesspoint?
It’s simple and just as easy to undo as “Router mode”.
If it should work against all expectations this time, haha, don’t forget to change the DNS server to 220.127.116.11 and / or 18.104.22.168
Hi @Axel_Lesch The previous router was not running in AP mode, and neither is the current one. And again, all the router questions seem, in my view, to be less relevant in view of the fact that the only software having a problem with any function is Roon. It’s difficult to imagine that no other application or device would have a problem if my router were misconfigured in some material way. I have 32 devices on this router and other than the Roon core on a fairly muscular PC with a wired connection to the router, there aren’t any issues.
Update. Okay, so the problem turned out to be that Windows apparently set my network profile as “public” in conjunction with the change in router. I never even looked at the d*$#&ed adapter settings since nothing else was wrong. Evidently this matters for Chromecast devices (and I expect for Android ones as well if they want to talk to a service on my PC). So that’s that. I have not met my own troubleshooting standards on this issue.