Nucleus One not loading correct IP address on network (ref#8IGHH2)

Support Nucleus Support
1

What's happening with your Nucleus?

· Nucleus turns on, but I can't connect to it

Is the Nucleus showing up after pressing the Configure RoonOS button?

· No

Please try to reboot your Nucleus

· false

Please try rebooting your network equipment

· false

The Nucleus HDMI output can provide very useful diagnostic information. This process will involve connecting the Nucleus via HDMI to a TV or monitor and then checking to see what is being displayed.

· Yes, I am willing to try the HDMI test

On the Nucleus HDMI output, what do you see?

· "Roon OS Web UI can be directly accessed at [https://xxx.xxx.xxx.xxx/](https://xxx.xxx.xxx.xxx/)" and the address is NOT http://169.254.XX.YY/

In the Roon app, please try to click on the "Select a different Roon Server" button. Are you able to reconnect to Nucleus from the list?

· I pressed "Select a different Roon Server" button, but I still don't see the Nucleus

Please check to ensure that your Roon remote is on the same network as the Nucleus and not connected to a VPN.

· I checked these options, but I am still not able to connect

One of the most common causes of this issue can be a Firewall blocking the connection for the Roon Remote.

· I have adjusted/verified the Firewall settings but I am still not able to connect

Describe your network setup

All of my household equipment is connected to Wi-Fi or wired to a Cisco switch. IP addresses come from the DHCP server in the Google Fiber gateway. Local IP addresses all start with “192.168.86.xxx”. The Nucleus One has IP address 172.27.35.12 according to its HDMI output. None of the Roon clients in the house can see it. Where is it getting that bizarre IP? It’s plugged into the same Cisco switch that all the Roon clients are connected to.

Describe the issue

My old Windows-based Roon server still works. I disconnected it and replaced it with my new Nucleus One. But the Nucleus doesn’t load an IP on my network and instead takes the IP 172.27.35.12, so nothing else on the network can see or communicate with it. “

2

Hi @Robin_Ballard,

I do not have Nucleus (or ROCK) but I seem to recall that when it boots it displays whether it configured for a static IP or for DHCP. Can you reboot it and watch the HDMI display for any additional info.

I’m wondering if the Nucleus One has somehow been configured with a static IP address, if so this should help …

1 Like
3

172.27.35.12 is a private IP in a range often used by VoIP devices, likely assigned by some DHCP server reachable from the Nucleus. Are you sure there’s no other DHCP server on your LAN, or that the Google Fiber gateway is not assigning such an address for some weird reason? Alternatively, as @Carl noted, someone might have set your Nucleus to that address as a static IP…

1 Like
4

This is not the 1st incident of this arising with a new N1. Coincidence? How would anyone have set a static ip on a brand new machine?

7

Hey @Robin_Ballard,

Thanks for taking the time to share your report!

I wanted to check in and see if you were still running into odd IP issues? Were you able to reset your network settings on the new Nucleus? Steps below just in case:

As a next step, lets reset the network settings on the Nucleus. Steps to follow below:

  1. Connect the Nucleus to a monitor or TV via HDMI.
  2. Connect a USB keyboard to the Nucleus.
  3. Power on the Nucleus and let it boot.
  4. Press ENTER
  5. Type resetnetwork
  6. Press ENTER

Let me know if you’re able to connect afterward.

Can you also provide more details around your VPN use?

Thanks! :+1:

8

Yes, I’ve reset the network settings and many other things. The NIC continues to be non-functional no matter what I do. If I connect an external NIC, the Nucleus works normally, but that is not a solution I can use permanently. And when I go back to the built-in NIC, it moves to an IP of 172.27.35.12 no matter what. The DHCP server assigns it an 192.168.86.xxx address, and it doesn’t use it. This is a hardware problem with the NIC.

9

The DHCP sees the Nucleus’s query, and tries to give it an IP on the subnet 192.168.86.xxx. The Nucleus ignores this, and loads 172.27.35.12 no matter what. In settings I even was able to set a static IP, but the Nucleus ignores it. I’m pretty sure this is a defective NIC.

11

Hey @Robin_Ballard,

Thanks for the update! While our team investigates this issue further, have you attempted to reach the webUI of the Nucleus yet?

You can access it by typing in the IP into a web browser -

Please share a screenshot if you’re able to gain access here. Thank you! :pray:

13

I wasn’t able to access the nucleus one at that address. But when I connected an external NIC, then I could access everything normally. Pity there aren’t more USB connections available! With only 2, I can’t spare once for an extra NIC.

I returned the Nucleus to y’all. Hopefully the replacement will work better.

15

Hi @Robin_Ballard,

This thread will remain open should any issues arise with the replacement unit. Please keep us posted. Thank you!

1 Like
16

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