Use a web browser and browse to the IP address of your NUC. See this KB article.
Let me add that:
- During these drop events, I’m unable to reach the Roon CORE web UI.
I notice that the Ubiquiti switch is a managed switch. Managed switches can be problematic in a Roon environment, as a search through the forum will show. I’ve been stung myself.
Thank you for that.
I can imagine how a managed switch might cause trouble in the path between the Core and Bridge. But in this case, I’m nearly certain that there’s trouble (maybe “also trouble”) between Controller and Core. And, I can’t for the life of me understand how a managed switch might be problematic in that path (especially one that’s worked without trouble for 9 months).
Try a different ethernet cable between the Core & the switch?
That I’ve done. Ug.
Thanks for confirming that the Web UI is also not available during this time. Since this is the case, it’s not necessarily a remote > Roon connection issue — The device isn’t being seen over the network for Web UI access either.
We make a note of some issues that can arise when using a managed switch in our Networking Guide, and have some settings that we recommend here as well. While I understand that things were working previously, we have seen issues like this come up relating to these types of switches, so bypassing that switch as a test would definitely be a great data point for understanding where this behavior is stemming from.
So. I’ve listened to your feedback and I have removed the managed switch from the path and added an unmanaged Netgear. Same deal. Not sure where to go from here…
It sounds like you have a local network issue. Break things down to the simplest configuration and see if things work then.
Forced a clearing of the ARP cache, and everything’s good. How odd, remarkable.
Hi @Jonathan_B — I’m glad things are now working for you. Just to confirm, is everything still performing okay? If you see this issue return please let us know!
Was that the ARP cache in the managed switch or the server? Helps point people in the right direction if they do a search on a similar issue!
Or just recommend turning off everything in the chain, counting to ten, and slowly powering it all back up again…
I do not understand root cause. Saying “network” or “managed switch” is not to point at an actual explanation of the problem.
These drop events, which would reoccur about every 60 seconds, began on a mature, stable network that hadn’t undergone any recent changes. And, no manner of power cycling cleared the problem.
I made two changes, which have resulted in a return to stabile operation: Placed an unmanaged switch in the path between Core and Bridge (though the managed switch continues in place) and delegated the Core a new IP (which would have had the effect of clearing the relevant entires in the ARP cache).
What I should do next is remove the unmanaged switch and see if the problem returns. My suspicion is that it will not. Why do I think this? Because the Web UI just stays up, when before it would go down during the drop events – and to reach the Web UI from my point of observation requires transiting a path over the managed switch, which is why I do not think the managed switch has played a role in these trouble. That said, so many times have I been wrong before and expect to be again.
I’d be curious to know more about the networking between Core and Bridge.
I can’t answer too many of your questions except to say that in my opinion the reason why managed switches are disliked in relation to Roon is because it is difficult to understand why Roon will misbehave with them in circuit.
Multicasting is important to Roon, often not important to other home applications, and frequently messed up by managed switches and some routers.
I don’t pretend to understand all this, but learned a LOT from the posts from @ipeverywhere in this thread, starting around post #10.
Why are you using static addressing?
If you are using a static IP, this could be part of the problem.
What you want is to set address reservation in your router software. It will accomplish what a static IP would, but without the possibility of IP address collision that would occur when DHCP tries to assign your static IP to another device.
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.