DLNA (Digital Living Network Alliance) is the industry standard making all kind of AV-gear communicate with each other over the home network. It allows you to control one device with an other, stream audio or video over the network, etc.
It is gaining momentum. What TCP/IP is for the internet, will DLNA become for AV-gear, a standard everyone adhere to.
JRiver is no exception to this rule, they support DLNA
They don't use the Windows DLNA components, they have rolled their own.
This has been done using JRiver 17.0.71 and Android 2.3.6
My mobile runs Samsungs AllShare

JRiver must have the Media Network on.
DLNA Server must be on if you want the mobile to browse the library.
DLNA Renderer must be on if you want to play the content on the mobile in JRiver on the PC.

The mobile can play the library on the PC on the mobile or on the PC running JRiver.
The reverse doesn't work, JRiver can't load the library on the mobile.

JRiver can't handle DLNA devices not supporting the "search" function.
The following testing is done using MC 14.0.158 on both client and server

Enable DLNA in options.
To access a server, MC must be up and running on the server.
On the client, you must enable DLNA too.
Both server and client run MC 14.

This time the MC interface is not really intuitive. In WMP all DLNA devices simply pop up in the navigation pane. In MC it is a bit hidden as it appears as a library in the File menu
You can have multiple libraries on the server but only the one chosen there will be displayed.

Now you can browse the library of the server.
There is one difference compared with a local library.
Normally MC thinks an album is an album if album title and album artist are the same.
Using DLNA an album is an album if album title and artist are the same.
This results in all samplers being split by artist.
This problem has been solved in JRMC 15.0.136. Samplers now display as one album..

The NAS (Qnap 119, firmware 3.1.0 build 0708T/ Twonky Media 4.4.17) appears in the library menu but selecting this library generates an error.
This problem has been solved in JRMC 15.0.136 by increasing the timeout for a file request.