What’s happening?
· Other
How can we help?
· I'm having trouble with my Nucleus hardware
Other options
· Other
Describe the issue
Roon not seeing server
Describe your network setup
Router to roon nucleus
When I was able to see the Nucleus it showed the ip address as 192.168…yet my pc shows 192.168…
Is this the reason now my system cannot find the Nucleus? If so how do I correct?
Thank you
Setup is router, to Bonn N8 switch, connected to Nucleus. Always been this way. I should point out that a day ago I was having an issue loging into a website, they recommended turning off my router and the turning it back on. This did the trick and allowed me acess. However the Nucleus connected first time today with no issues, only when I tried to start a song over it lost connection.
Now my pc says a different ip address?
I just tried again restarting the Nucleus again, this time it connected.
Not sure what exactly transpired, however all is now working. Can you explain what happened?
Firstly, you should not publish your public ip address (the one in the image in the above post) on a public forum. It becomes a security risk.
There is no security risk to publishing ip addresses starting with 192.168…
IP addresses.
You are getting ip addresses confused.
The public ip address as reported by the ‘what’s my ip address’ web site is usually (it can be a bit more complicated) the WAN side ip address of your router. That is the IP address of the WAN port that connects to your ISP service.
Your router is given, in its settings, a different ip address for the LAN side of your network (ie the internal network to which all of your computers, phones etc are connected). This LAN ip address range usually starts with 192.168. (although it can also legitimately start with 172.x. [where x is in the range 16 to 31] and 10.). Looking at the ip addresses that you have stated, I would guess that the routers LAN side ip address is 192.168.254.1 (or maybe 192.168.254.254).
The router also has a setting called the netmask which is usually set to 255.255.255.0. This basically says that the first three numbers of the ip address (192.168.254 in your case) define a ‘subnet’ and the last number identifies a device on that subnet. Each device connected to your network is issued a unique device identifier part of the ip address but they all share the same subnet part. Thus all your devices will be 192.168.254.x where x is different for each device.
Consequently, it is perfectly legitimate for your PC to have the 192168.254.102 ip address and the Nucleus to have the 192.168.254.155 ip address since they are different devices. Both these ip addresses are within the same subnet (again assuming your netmask is 255.255.255.0).
Nucleus Connection Issue
With the above in mind, the ip address that you used to be able to see the Nucleus on is perfectly OK and will not be causing your current connectivity issues.
If you can, you should connect your Nucleus to a TV or a computer monitor using one of the HDMI ports. If you do this, when you power up the Nucleus, you should see some status text - includeing the ip address of you Nucleus. If you don’t see any text, there is likely a hardware issue and you will need to get assistence from official Roon support before embarking upon the next actions.
Another possibility is that you see some text but the ip address is not shown. Take a photograph of this diagnostic text you see (if there is any) and post it in a reply in this thread.
In this case, there may be a hardware issue with the Nuclues, or it may be a network issue. You could try some simple actions like trying to connect the Nucleus with a different ethernet cable or connecting it to a different port of the device to which it is connected to (Presumably the Bonn N8 switch). Sometimes ethernet ports fail and just using a different port will fix the issue. You could also try connecting your Nucleus to the router instead of the Bonn N8 switch. Even if you are connecting your Nucleus to audio endpoint devices by USB or HDMI, you can move the Nucleus (temporarily) to anywhere on your network (disconnecting from HDMI/USB audio devices if necessary). This will allow you to see if you can then observe the Nucleus on your network. If you can, then maybe the switch is faulty. Again for experimental purposes, you can use any network switch you have to hand to replace the Bonn N8 switch. If the Nucleus works properly with a different switch, then the Bonn N8 is likely the cause of the issue.
If you can’t easily connnect a monitor, you may be able to look at the ‘connected devices list’ in your router usually by visiting its web admin pages or, for some routers, using a phone app. If you don’t see it listed, then the issue is likely to be one of the hardware/network issues above.
If you do see your Nucleus in the device list on your router, it should tell you what ip address is assigned to your Nucleus.
1 Like
Sorry. I didn’t see this post before I posted the above reply. Maybe I had already started my reply when you posted the above.
There are a few possibilities as to what may be going on.
First, there may be an intermittent problem with the ethernet connection to your switch or with the switch itself. Check to make sure that all the network connections are secure. If this is the cause of the fault, if/when it happens again, if you connect the TV or monitor to your Nucleus, you should see the diagnostic text on the TV/monitor indicating that every this OK except that you will not have a valid ip address (one starting with 192.168.254.).
It is also worth noting that it may be an issue with the Nucleus. It could be an intermittent fault - maybe temperature related with the Nuclues - or, more likely, is could be a fault with the OS SSD in the Nucleus such that there are occaisional read issues which can cause a boot failure. If this is the case, when it happens again, and you connect a TV/Monitor to the nucleus, you may see no text on the screen at all (complete boot failure) or you may see an error message indicating that something went wrong during the boot.
I did, Thanks
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.