Hello @raykkc
Thank you, and those two addresses settle one thing straight away: 10.0.4.55 and 10.0.4.89 are on the same network, so the subnet question is closed. That is not your problem.
What we can tell you is that we see nothing at all from your Antipodes. Not a server we cannot reach, but no Roon Server reporting to us whatsoever. Combined with the detail that the unit was switched off for over a month, we think we know why.
On 20 April this year Roon’s minimum system requirements changed. The new version needs a newer underlying operating system than some older music servers provide, specifically glibc 2.27 or above and openssl 1.1.1 or above:
Your Antipodes runs its own operating system, called AMS, and whether Roon Server can still run on it depends on which AMS version the unit has. Antipodes have confirmed on their own forum that AMS v4 and v5 meet the requirements. Someone with an older version reported exactly your symptom, being unable to connect to the server after the Roon update, and Antipodes told him the unit needs its software updated at a service centre:
So the one thing we need from you is this: please open the Antipodes web interface and tell us which AMS version it is running. It will be shown on the main or system page.
If it is v4 or v5, then something else is going on and we will keep digging with you.
If it is older, then Roon Server can no longer run on that unit until Antipodes update it, and that is a conversation with them rather than with us. We would rather tell you that now than have you spend more time on your network, which is fine.
Please also confirm, while you are in that interface, whether Roon Server is shown as the selected application and whether it reports as running or stopped.
Sources: Roon minimum system requirements changing on April 20, 2026, New roon on 20 April, Antipodes User Forum