Hey @Vladimir_Grayvoronsk,
Thanks for the reply, and my apologies for not providing more insight into what might be happening.
In Roon’s architecture, your Server (on the NAS) and your Control (the PC) need to have a constant, open conversation.
The fact that you can ‘see’ the server but are stuck on the loading screen means the PC knows the server is there, but something is blocking the actual data from flowing. There could be a few reasons for this, one of them potentially being the two separate subnets I’ve mentioned above.
Every connected machine in a local network receives a specific IP Address, and each IP Address is nestled within a subnetwork. Roon requires all devices to be on the same IP range, so any devices used by Roon can’t be on a different subnet than the device running Roon Server. This includes remotes and endpoints. This means they must share a similar address, just like all buildings on a campus have the same main address, but different building numbers.
How can I tell if my devices are on the same IP range? First, you need to determine the IP address of your devices.
An IP range will be something like 192.168.1.x, and ‘x’ changes for each device on the network. For example, your server machine might be 192.168.1.4. If this is the case, you’ll need your remotes and endpoints to also start with the same first 7 numbers in the IP scheme 192.168.1. If those first 3 sets of numbers are different, then they’re on a different subnet.
You can check the IP addresses of your devices by accessing your Router settings, and then selecting typically a subsetting named “Devices” or “Devices List.”
If you’d like, we can help you navigate these settings, just let us know what make and model router you’re using, along with any other network gear in your chain between your Roon Server and your primary router.
Thank you @Vladimir_Grayvoronsk 