Servers: Are we there yet?

Yeah, as a veteran in the software/cyber industry it is my experience that MOST software sucks, so I am not surprised at this in a music server. 
...However, you might do some discovery work here: The server has at least one IP address (wireless and/or Ethernet), have you tried accessing it directly via a web browser? (As in http://?.?.?.?  ...where ?.?.?.? is the 4 octet server address.) The server may express its service management through a web server that you could navigate.

@djohnson54 @sbank @psag I say this as a cyber security guy: Devices that allow connectivity to and from the Internet (actually ANY network) represent a danger to other devices in your network that will subsequently develop a trust relationship with said Internet-connecting device.
You absolutely need to understand that your home network now has devices in it that run software that came from whom?That is just a simple fact today and alone it should not stop you from using them, but you need to mitigate against those mechanisms being insecure (who wrote the server code, who configured it?). Think of these devices as requiring constant immunization otherwise every other device might also get infected...
What to do? You have several strategies, at minimum you need to lock down your Internet facing router and perhaps add a second device (such as a firewall) between the server and the router. That acts as a second level of defense against door-rattlers, knob-turners and server-probers who are sitting in their moms basement on their junior high laptop.
The reason for all that above is two fold: First, create awareness that IP devices are dangerous to your home network if they are insecure; Second, to complain at how poorly such devices generally are configured and that if the vendor gets enough calls from us they might do device security better.
QUESTION: Has anyone seen ANY penetration analysis results for any of these music servers? 

@almarg
After I wrote my post re connections from the internet (and you replied) ...I should add that there is a simple and reasonable approach to mitigate the concerns I raised: Stand up a separate and independent wireless or ethernet network for "foreign" devices.

By example, in my home I have a Verizon wireless router which essentially provides connectivity to the Internet. This router can be configured in several interesting and useful ways by the owner.

One important way is to create two or more separate networks that only pass traffic through the router and NOT to each other. If you trust a couple of your devices, then put those on your "trusted" sub-net; likewise, if you don;t know what the heck a device is really doing (or where it’s networking software came from ...China?), then limit it’s internet access to the other "UNTRUSTED" sub-net.

This is very effective, and easy to do with almost all ISP provided routers, if your ISP router can’t do this then buy an additional router (or firewall etc) that can and stick it in-between the ISP router and all your devices.

This strategy of "isolation" or network "segmentation" has an additional benefit and that is traffic management. High-bandwidth devices should send their traffic as directly to the ISPs router as possible, otherwise it adds to internal home-network congestion. So, in my house I have several separate and isolated networks, each has one or more wireless access points. The traffic from these separate networks can not cross network segments, it can only get directly to the ISP router. This alone makes my other segments unaffected by the congestion.