Everything is broken

Support
1

Roon Core Machine

Windows 10 Home - 22H2 (build 19045.3086)
Intel Core i5-6500
16GB RAM
Roon core on SSD, library on Synology NAS

Networking Gear & Setup Details

Motorola cable modem
Asus Zen WiFI AC (CT6) - 1 node set up as router, 1 node set as a mesh
Asus RP-AC1900 node (1x) with ethernet connection to router, through an unmanaged switch. PC is (ethernet) connected to this node.

Connected Audio Devices

Allo DigiOne (ethernet) - SPDIF coax to SMSL DAC
2x Chromecast Audio
1x Chromecast (older generation)
various phones, tablets

Number of Tracks in Library

21,700 tracks

Description of Issue

Since most recent update, neither ARC nor the Roon Remote on my phones or tablet are able to connect to the Core. If I restart the core, they can usually see it for a few minutes but then they lose the connection. Roon Remote doesn’t give an error, it just shows the pulsing Roon logo or a blank screen, but doesn’t revert to the “no core found” status until I restart the core.

I can still control endpoints from my PC; i.e., Roon on the Core PC appears to be operating normally, so it seems this is some sort of an issue with network connectivity.

Roon Core reports that ARC is working normally and visible via the network. The problem with ARC happens on both local wireless network and mobile network.

I’ve rebooted my PC several times and have rebooted the network as well, but no improvement. My PC is older, yes, but it’s been working well enough until the update.

Thanks, and HELP!

2

@Jamison_Smith, welcome to the Community. Just as a quick check, is the RP-AC1900 configured as another AiMesh node in your CT6 mesh network?

3

Yes, that’s the setup.

However, both Remote and ARC have been playing nice ever since I posted my request for help. Perhaps I scared them into submission?

Even so, I’d be interested in any thoughts you have, just in case this happens again. (which it inevitably will, just as soon as this thread is closed out!)

4

I’ll mark this as Solved for now.

No idea why these things happen, then randomly (it seems) starts working again. Sometimes a reboot somewhere in the network makes a difference, maybe it was a firmware upgrade to the RP node (one became available in May).

Glad you are up and running again.

5

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.