I set up Roon core on a QNAP, this appears to have worked OK
I had previously set it up on a desktop, but the trial lapsed
After some messing around, I can see the NAS core from the desktop
Main endpoint I’d like to use is a NVIDIA Shield, but I’d also like to use a tablet periodically.
The Shield seems to “see” the old core…and sees the Shield mixer as an audio zone
The desktop seems to “see” the new core, and only shows the NAS’s audio outputs as zones
None of my tablet, phone, etc, can see any core at all, they just get stuck at the “Choose your Core” screen, and trying the remote libraries or configure roon OS options don’t do anything
Desktop and NAS are hardwired to home router
Other devices are connected to home network over Google wifi, which is connected to the home router by ethernet
I was, I recall, able to use a tablet as a remote/endpoint with the previous trial installation
How can I get it such that I can use, for example, a tablet as a remote or as an endpoint?
Hi Jason,
this feels like a network issue. Am I correct that Google Wifi is not your home router?
If this is correct, can you check if all devices (especially the ones connected by Google Wifi and the ones on the home router) have the same IP range?
In many cases the default IP range is 192.168.0.x (and only the last number, represented by the x, should be different on each device)
Hi @Jason_Gogal ----- Thank you for the report and sharing your feedback with us. The insight is appreciated! Sorry to hear of the troubles.
Moving forward, to “piggy back” on the suggestion made in @crieke’s post above (), you can also try an app like FING to scan your network looking for devices that it can “see”, showing itself in the process.
As you can see from your screenshot, , the DHCP server in the Google Wifi device will give out IP addresses in the range 192.168.86.0/24 - and it’s not changeable. If your router has a DHCP server giving out addresses in the 192.168.172.x range, then this is a different address space. The two networks are totally separate.
You will need to setup Virtual IPs (your router may or may not support this and may call it something else) between subnets and allow TCP 9100-9200 and UDP 9003 between the subnets.
I think the best solution is to disable one of the two dhcp servers. I am currently studying the manual of the Actiontec V1000H.
It should also be possible to deactivate the DHCP server on the Google Wifi, but it is not recommended by Google…
@Jason_Gogal: Is it possible to connect all ethernet cables directly to the Google Wifi devices (maybe with a simple network hub/switch)?
As I think about it, this may not work because the OnHub does not have the QNAP or Desktop on its network and would not be able to see them unless it could see VLANs.
You may have to connect the QNAP and Desktop to the OnHub so they are all on the same network.
Sounds like a good idea (if it is doable).
If nothing else is connected to the ActionTec V1000H, you could also think about using this device only as a modem and establish the connection to the internet (VDSL2?) directly by Google Wifi.
I’d also recommend to save your config files from all involved devices on your computer, so you will be able to revert back easily to the current config.
Ahh, ok. If you also have a fiber modem, can you take out the ActionTec completely out of the equation?
(I have to admit I have no experience with fiber devices…)
So, you currently have a fiber modem that is connected by ethernet with the ActionTec Router?
(Just wondering as the ActionTec is listed as a VDSL2 router/modem).
Then my guess is that the ActionTec has nothing to do with your internet connection.
You could try it by connecting a computer directly to the fiber modem. Eventually you have to reboot the fiber modem if you connect a different device to it, as the fiber modem might lock to a specific Ethernet MAC address (this is also the case with my cable modem). If that works, I’d connect your fiber modem directly to the WAN port (the one that has the Globe icon) of your Google Fiber Base.
I currently see no reason to keep the ActionTek device in your network chain…
I rerouted all the devices through the outbound port of the google wifi. Then I found that my NAS was bricked. So I plugged its second ethernet port into the router and made both of its ports static. Now everything that matters is on the 192 network and I can control the Shield endpoint running Roon from the NAS from my iphone. I assume it will also work from my tablet now.