BTW, this is after I had rebooted everything - the modem, the router, the nucleus, and the Ipad.
Sounds like a network issue. Everything has to be on one IP range.
I rechecked that the router function was turned off from the Viasat modem (otherwise I would have two networks trying to work). So after being reset how are the Ipad and Iphone still attempting to connect to a discontinued IP address? And more to the point how do I direct them to the proper one/
I have a similar problem using iPad as the control device for Roon on one of my systems, and as Paul has intimated, the problem has not always existed. My setup used to work flawlessly until around (at a guess) 6 months or so ago.
I have Roon Rock installed on an Intel NUC (8i5), and my ‘older’ iPad Air is currently running OS 12.4.6. My high(ish) speed broadband and WIFI is provided by Sky (UK), and delivered by a relatively new Sky Q router, and I also have a 2 Tb Sky Q TV box (PVR) which is also connected to the network. I have a Cisco 2960 switch attached to the router over ethernet, and the following components connected to the switch: Intel 8i5NUC; Panasonic 4k Blu-ray player; Panasonic 4k Smart TV and a sonore MicroRendu audio streamer/renderer.
My problem is similar, but not exactly the same as yours. Whenever my Sky Q TV box is connected to the router via ethernet, my iPad Air cannot find my Roon NUC. I get the same Roon Logo and message (“looking for your Roon core”) as described by Paul.
However, as soon as I disconnect the Sky Q TV box, my iPad instantly finds the Roon NUC and works perfectly. No other device on my network is affected in any way - just the iPad to Roon Rock connection.
My solution, although a bit inconvenient, is to leave the Sky Q TV box unconnected when I am listening to music and don’t need it, and to physically connect the Sky Q box when I do need it.
I use a Windows 10 PC as Roon control point for another hi-fi system elsewhere in my house, but connected to the same home network via ethernet (on a separate switch). The Roon control app on this PC has no issue finding Roon Rock on the Intel NUC irrespective of whether or not the Sky Q TV box is connected, so I guess my issue is purely wi-fi related.
I would prefer a more convenient solution!
Success Finally! The gentleman who commented this must be a network problem (although I could not see how) was right. I had disconnected the network function of my Viasat modem/router and checked doing so twice. Nowhere in the online Viasat instructions did it also point out that having done a hard reset was also necessary which required t depressing a small pin hole button with a paperclip for a minimum of 30 seconds. Prior to my doing so ter Viasat was still trying to provide the old network confusing Roon. As soon as I did the hard reset my remotes were able to connect to Roon. Psheew! .
I knew because I hang around on this forum too much
To my great surprise, as well as resolving another issue of mine involving ‘missing metadata and artwork’ in Roon Radio, release 571 also appears to have resolved the issue I outlined above. I was losing connection from my iPad to my NUC whenever my Sky TV (PVR) box was connected to the network. Following the update of release 571, this problem has disappeared. I can now connect from my iPad to the NUC on which Roon Rock is installed even when my Sky Q box is connected to th enetwork.
Unfortunately, I have to report that this problem has recurred. Today, for whatever reason my iPad was not able to find the Roon core on my NUC until I disconnected my Sky Q (PVR) box from my network.
At least the other more irritating metadata related couple of issues that I had post release 1.7 and which appear to have been resolved by build 571 have still not recurred.
I just started using an Ipad and had a problem finding the Roon Core on my Windows 10 PC. My Android phone also failed after working all through my Roon trial. A new router was installed and I believe this changed some settings in Windows 10… After many attempts to connect from the controllers I changed the setting for network type from Public to Private and my Ipad and Android phone connected instantly. Hope this helps.
I am having similar problems with my iPad (Mac based computer system, my iPad has the iPadOS14.2) which is unable to connect to my Roon Core. I did not have any problems before. I have a Roon nucleus, the Roon app on all my other devices (iphone, imac) function flawless. All the devices are connected to the same network. I have already restarted my ipad, Roon nucleus and router. I have also used the IP address of my Roon nucleus in order to find the Roon core, without success. Does anybody have a suggestion?
iPadOS14.2 introduced more security features, and apps have to be specifically authorised to access the LAN.
Go into the iPad’s setting and adjust them to grant access.
Alternatively, uninstall the Roon iPad app. reboot the iPad and then reinstall Roon … on reinstallation the iPad will prompt to allow access for Roon.
Great! Uninstalling Roon iPad app, rebooting and reinstalling Roon solved the problem,
Found the privacy setting in the iPad, and was able to turn on the LAN access. Thank you very very much!
There are two pieces to LAN / Wifi connection. On is an IP address of the device that sends the signal and MAC address of the device that receives the signal. Once you setup your LAN connection for the first time, your device gets registered by your router with its unique ID number (MAC address). Router’s DHCP assigns IP address for your device many times. In order to start fresh and reset all network settings for your device you will have to change MAC address, this way router will recognize it as new device. Each device can generate new MAC address.
Sorry Peter, that’s not how it works and is bad advice.
A device’s MAC address (set in the Network Interface Card NIC) is typically fixed and defined by the manufacturer (I acknowledge that some specialist devices allow the MAC address to be user configured but these are quite rare.)
When a device is setup to use a DHCP assigned IP address, the device broadcasts to the router and requests an IP address. The router then assigns one (from the DHCP pool) are records that IP against the device’s MAC address.
The leasing of that IP address is typically 24 hours, after that if the device is no longer active the router may release the IP back to the pool so it can be reused.
On most routers, there is a user option to “fix” this reservation indefinitely then the IP address does not change even after reboots … (this is what I do, rather than configuring the device itself to have a static IP address).
For more information check out …
After I wrote my post I realized that I made a mistake. You are right about that MAC address is generated by the device, but it can be changed.
MAC address is hard coded as far as I know.
The Mac address of the network card is but you can spoof one in the OS.
My experience with MAC addresses comes with setting up VM (Virtual Machines). I had to reset network settings for Windows 10. Either way, MAC address is software generated and some vendors may restrict access to it. Other possibility is to remove registered device from router or reset router to factory settings and start over.
Simple and effective.