Roon Remote on iOS stopped connecting to Core after Day One of Trial

Support
1

Roon Core Machine

HP Spectre Laptop
Windows 11 Home 10.0.22621 Build 22621
Intel(R) Core™ i7-10510U CPU @ 1.80GHz, 2304 Mhz, 4 Core(s), 8 Logical Processor(s)
16GB RAM

Networking Gear & Setup Details

Netgear Wi-Fi Router with eero Mesh, No VPN, McAfee LiveSafe on Core machine
Firewall opened for Roon and RAATServer applications
Port forwarding for UDP 9003/TCP 9100-9200
All components (laptop, iPad, iPhone, eero, router, cable modem) in the same physical room

Connected Audio Devices

Windows System Output

Number of Tracks in Library

2800 Tracks so far (on an external USB SSD drive), but ripping continues

Description of Issue

I am now starting Day Three of my Roon Trial, just using my laptop for now, but intending, if all goes well, to migrate to a standalone Core, a separate DAC endpoint, and an iPad for control via Roon Remote.

On Day One, after adjusting my Firewall (see above), I had no trouble at all getting my iPad to discover and connect to my Core and control my audio on the laptop. I even got Roon ARC running on my iPhone straight out of the box with no troubleshooting required whatsoever. Even via the LTE network, not just the local Wi-Fi. Roon Remote worked on the phone as well.

But at some point on Day Two, Roon Remote on both the iPad and the iPhone began to refuse to find the Core anymore, while Roon ARC continues to hum along just fine on the iPhone.

I’ve attempted the traditional process of deleting the Roon Remote app and its data, performing a “hard reset” of the iPad, and then reinstalling, with no luck. Giving the app the IP address of the Core does not help either. Rummaging around the Support forum hasn’t provided a prescription I haven’t tried yet…

The troublesome iPad is an older model – an iPad Mini 2, running iOS 12.5.7 – that no one in the family uses anymore. But that makes it the perfect dedicated display/control device to replace the iPod Classic that currently sits on my desk next to my DAC :slight_smile:

The phone is newer – iPhone X with iOS 16 – and it still works with ARC, just not Remote anymore.

What baffles me is that everything worked perfectly on Day One … and the Roon ARC setup still works, both on my local Wi-Fi and via Comcast cable → AT&T mobile networks.

Is there some kind of Core setting or other network issue that could have morphed without my awareness between Day One and Day Two that would prevent Remotes from local discovery but permit ARC to keep going? Or some iOS issue (impacting two devices simultaneously after 24 hours or so)?

It all seems upside down … ARC is supposed to be the challenging problem, not Remote :frowning:

What should I try next?

2

Hello David and welcome to the community.

Is the Laptop or whatever your Roon core is running on connected to the router with Ethernet or Wi-Fi?

Wi-Fi works in some situations, remotes and some endpoints, but Roon is a heavy Network user and Ethernet from core to Router is recommended.

3

Thanks, Mike, for the quick suggestion!

I am using Wi-Fi so far, for this initial Trial. I understand the value of wired Ethernet for the Core, and fully intend to use it for an eventual standalone Core once the Trial convinces me that Roon is the way to go for me :slight_smile:

Unless another solution emerges, I will attempt an Ethernet link for the laptop later today (it will require some juggling of other network devices), to see if that makes a difference.

I would be more inclined to blame Wi-Fi if I were having trouble streaming, or browsing the library, or some other data-intensive network operation. But given that ARC is consistently working perfectly on one device, while Remote on both that device and the one next to it cannot even locate the Core, even when I supply its IP address, I doubt bandwidth is the issue here.

I don’t know the innards of the protocol, but I would hope the discovery mechanism is lightweight enough to work with the setup as it is.

I will report back once I can flip to Ethernet. Thanks again.

Meanwhile, other suggestions are still welcome …

4

Lunchtime update: Connected my laptop to my router via Ethernet. Disabled Wi-Fi on laptop to force Ethernet as the only path out of the Core.

iPhone works fine with ARC – including finding and streaming new albums as I rip them to my USB drive

But the same iPhone running Remote cannot find the Core. My iPad likewise cannot find the Core. Both remain stuck at “Looking for your Roon Core” even when I supply the Core’s new wired Ethernet IP address.

Was hoping for a quick fix, but still stumped :frowning:

5

@drw, can you confirm that your Spectre’s network setting for either WiFi or cabled Ethernet is set to “Private” rather than “Public”, and your firewall exceptions in both McAfee and the Windows firewall are set to allow for exceptions for roon.exe and raatserver.exe via the Private network option?

6

Thanks, Robert. I believe the problem was my Ethernet was defaulting to “Public” rather than Private. When I switched it over, everything connected again :slight_smile:

I’m not sure I understand how it ever worked on Day One, as I never touched the Public/Private settings in the Network control panel, but … Windows must retain its mystique :wink:

(And thank you again, @Mike_LC, for your advice earlier today).

Of course, taking the Network Private broke Roon ARC, but a wee bit o’ port forwarding made that work again.

Everything is working great now, which makes me a Happy Trialist once more :slight_smile:

Next step is installing RoPieee on this Pi4 I’ve had lying around, hook it to my new Topping DX3 Pro+, and enter the world of remote endpoints. Wish me luck.

1 Like
7

@drw, glad to see you have it resolved. I had this issue last week with a Windows 11 update; sometimes Microsoft updates fallback to a more secure setting, but it takes awhile to determine what happened and where to change it.

Hope you are enjoying your music again!

8

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