ROCK, NUC8i7BEH, Crucial 8GB Single DDR4 2400 MT/S, Transcend 128GB Nvme PCIe Gen3 X4 MTE110S M.2 SSD Solid State Drive
Networking Gear & Setup Details
Synology DS920+ NAS connected to Intel NUC
Connected Audio Devices
MacBook Pro, iPhone 13 mini, Chord Mojo2/Poly, Chromecast Audio, Apple TV 4K
Number of Tracks in Library
45,000
Description of Issue
I continue to try to solve the problem that I described here. Through the process of elimination (swapping the router, reducing and now perhaps eliminating the switches), I hope to resolve the issue.
I am attempting to eliminate the switch from my network configuration after Synology advised that I can connect my router directly to my NAS at one ethernet port and Roon ROCK at the other. When doing so, I no longer see Roon ROCK.
What do I need to do in order to launch Roon?
Here are some screenshots that better describe the situation:
I am not going to call myself a networking expert, but this feels so wrong. By unplugging the NUC from the router and plugging it into the Synology, you are basically expecting your NAS to function as a switch. AFAIK it does not do this. Even if you can establish a connection between the NAS and the NUC, the NUC will not see the rest of your network or have internet connectivity, which is a requirement for it to function.
In theory, you can configure your Synology NAS as a router but I would not recommend this as it add unnecessary complexity on the NAS and will still require a switch on the LAN port of the NAS.
I am not familiar with Google routers. If they have more than 1 LAN port, you can connect both NAS and NUC to a LAN port on the router. If your router has a single LAN port, you will need to connect that to a switch and then connect both the NAS and NUC to that same switch.
You are correct. In writing my fatigue-addled, late-night response yesterday evening, I was mistakenly thinking the Synology would handle the internal switching/ routing to make this possible. It doesn’t–I just tested it on my setup. It might be possible to configure some kind of vSwitch, but this clearly would not be worth the effort. I’m not sure why Synology recommended this to the OP. So, I’ve taken down my prior post so that no one gets themselves into a problem.
To the OP @David_Weinberg, there is about a zero percent chance that eliminating the switch will solve your problem. If you really want to rule out your current switch, borrow a different one from a friend and swap it out. Your issue is clearly something to do with sending AirPlay to your Chord Poly over the “hotspot” when you are remote. I have no idea what the problem is, nor can I help you because I don’t own the hardware. What I can tell you is–you might have 99 problems, but the switch ain’t one of them.
Okay, thanks for clearing that up. I reconnected the switch and was able to reset the NAS and can now access it (I wasn’t able to do so earlier). I am still unable to access Roon. When launching Roon, it is seeking out the static IP address I plugged in earlier and never latches:
Did you switch the ROCK back to DHCP? If not, and if you can get back to the ROCK’s config page (would be at http://192.168.86.40), be sure to set the the IP Address Setup to DHCP, then save and reboot. The ROCK will pick up an IP address from your router, and all should be as it was.
If the ROCK has already moved to a different IP address, look in your router’s DHCP lease table and see what the new IP address is. You can then get to the config page there, to see what is up with your network settings.
BTW…for clarity, your ROCK is connected to the switch, not the NAS, correct?
Further info: the message you received “Failed to load device state…” came from the ROCK, so actually the network connectivity is working. You can find several threads on this forum that deal with this error message–I would guess that the Roon server software has not initialized properly. If you can get to the config page, you can restart it. Otherwise, I’d shutdown the ROCK (brief press of the power button should trigger a graceful shutdown), and then restart it. Hope this helps…see the other threads for further ideas.
