Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
Modem in bridge mode, Asus ax11000 in router mode
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
PC as remote, and iphone
Description Of Issue
Hi all, I have installed new router (old was tp link), nuc is plugged directly with ethernet cable. Router does not give ip to Nuc and the core does not show as a connected at all on router, when I turn off and on the NUC (with Rock installed of course) I sometimes get roon to see the core it tries to connect and fails a few times until it stops trying (or so it showes on remotes). I have enabled mutlicast routing and IGMP snooping, Anything I should do? I see that Asus routers tend to be problematic with Roon cores is there a fix coming?
Had a similar problem with my ASUS GT-11000 router, Got an 8 port Trends network switch from Amazon. Took all router ethernet inputs out except the modem input and hooked them into switch. Problem solved.
Funny!! I’m having a similar problem tonight! Just purchased an Asus RT-AX58U as I’ve got quite a few Apple bits so wanted to take advantage of the Wifi 6 ax speeds…
Everything wireless connected up fine and working well.
Roon Core (Intel NUC like yours), connected directly to the router via ethernet cable. Can browse the network from my Mac and see the storage folder etc. But when I launch the Roon Remote on my mac, it can’t find the Core!
Saw on some other threads to start by turning off the firewall… made no difference until I restarted the Roon server software - then the remote software opened up fine.
But if I close it and open again, same issue - cannot find the core. So something’s definitely amiss. I don’t want to be restarting the room server software every time I want to use a remote!!??
Did you have your core NUC on a static or reserved IP address on your previous router? I just bought an Asus router and the DHCP IP address range is different to my previous one so I had manually reset a couple of things including the IP address of my NAS where the music folder is.
When I restarted the Roon server, it seems to have picked up the DCHP details correctly. So unsure what I need to change?
But now every time I launch the Roon remote on my Mac, it won’t find the Core until I manually go to the IP in a browser and restart the server software - and that makes it work, regardless of whether the Asus router firewall is on or off! (Firewall is on right now - but it’s the exact same behaviour even if the firewall is off! Go figure!! )
iPad and iPhone found the Roon Core no problem - and both devices remembered what was playing on them last! Had a message on both about iOS14 and needing to allow ‘network discovery’… soon as I pressed ok, no issue with connection
IGMP snooping causes problems (sometimes) with Roon’s network discovery, so turning it off may help solve the problem.
Setting a fixed IP on a device itself is a source of endless problems because different routers and DHCP servers use different IP ranges. If you do want fixed IPs, use a router with a DHCP server that you can tell to assign that fixed IP to a particular MAC address (that’s what I do with my Ubiquiti EdgeRouter).
This is the strange thing @Fernando_Pereira… the web interface has the correct details already. (Which makes sense now - because every time I restart the server, the mac remote connects fine).
To see that pic from my last post, I signed out of the Mac remote and noticed that the remote software was pointing to that incorrect ip (ending 138). I can’t see how I can change it directly from the remote settings? It doesn’t need to be changed on the web interface as that’s already correct?
After restarting the Roon server software - so I can connect with the Mac remote (iPhone and iPad absolutely no issue)… In the Settings - General area of Mac remote, shows me signed in and IP in the ‘Core box’ is also correct!
However, when going to Settings - Setup - Configure Roon OS devices and then clicking on the Configure button… it’s here where the IP address is wrong (underneath Roon Optimized Core Kit).
This is the issue methinks - and the reason why, when the remote is opened and can’t find the core - but the roon server is restarted, it connects!
All was working fine on the old router, without the need to configure a static IP or mess around with firewalls, IGMP etc
And as it’s only the mac software remote with this issue - and my iPhone and iPad connect to the ROCK fine without having to restart it, this is the only little hurdle I need to get over.
I’m wondering what will happen if I choose to select a new core rather than restart the server?