Netgear Orbi Router and 1 satellite
Century Link modem
Connected Audio Devices
Nucleus, Usb to Sabaj Dac
Orbi satelite, Ethernet to Allo signature, usb to second Sabaj dac
Number of Tracks in Library
Description of Issue
Worked fine yesterday. Has always worked fine.
No network/audio system changes for over a year.
Tonight, “cannot connect to core” message.
Restarted Nucleus, modem and router several times.
Nucleus seen on Orbi Router (screenshot)
Tried to connect to different core and scan for IP address, no luck (screenshot)
Not sure what else to try, or possible hardware failure.
Thanks Carl, but I remain a bit lost here. Not sure how to access the Web Administration page, although I know I’ve done it before. Roon will not let me go past the 'waiting to connect to core" screen. When I select settings from Roon’s dropdown menu, nothing happens. I must be missing a simple step.
Also, although the Nucleus shows it’s connected in the Orbi Router app, it does not appear and I cannot connect to it from my Mac Finder/network.
Thanks for everyone’s help. This is now resolved (I hope). For the sake of anyone who might run into this, here’s what I think happened, but I’m not certain.
Roon suddenly could not find its core and none of the standard troubleshooting worked.
I have a Netgear Orbi router. When ARC came out, I couldn’t get it to work, so I bought a tech support contract with Netgear that supports all attached devices. They resolved the ARC issues and it still works. Took them a while, though.
So I called them today after taking the obvious troubleshooting steps. The support person spent two or three hours on it and got it resolved. His take, if I understand it properly, is that my Nucleus IP address changed yesterday from xxx.xxx.1.1 to xxx.xxx.2.1. So, Roon could not find it. In a nutshell, he could not get the Nucleus back to a 1.1 address, so he changed the rest of the network and devices to the 2.1 address.
After checking out potential issues with the router and modem, he thinks the address change happened on the ROON side.
So, it’s working. I don’t really know what happened or why he had to fix it this way. Maybe someone can shed some light?
When using DHCP, which is the normal and recommended way (unless one assigns static IP addresses directly on the devices, which is a bad idea in most cases), the router assigns the IP addresses to the devices. The Nucleus doesn’t choose its own IP address. So if the router suddenly assigns an address from the xxx.xxx.2 network instead of the xxx.xxx.1 network, the problem should be on the router.
That makes sense and it’s how I thought it worked. I’ll probably call them back and ask about it. The Nucleus and other network devices were and still are on DHCP.
I spoke to Netgear support again about this. I verified that my router was set to DHCP when this issue arose and it remains so. They wouldn’t say why this happened or if it was an Orbi error, but that’s a reasonable guess.
