Antoine's system

[baconbrain]

Hi Baconbrain,

Sorry to hear it doesn't work out for you. I can think of three things to try in your situation (assuming there have been others for which NAA works in bridge mode, I haven't kept track).

If I'm not mistaken HQPlayer NAA uses mDNS (multicast DNS) for device discovery, at least it used to. This means that all hosts need to be in a single subnet/broadcast domain for them to be able to find each other. This is similar to Apple's Bonjour protocol (and other similar protocols like Zeroconf, uPnP, ...). Separate routed subnets won't work for these protocols which I myself realized yesterday after thinking over my own plans. If I'd go this path I'd have to sacrifice the Shairport (Airplay) functionality of the SMS-200 as it's anything but easy to work around this issue (I'd need some sort of software that proxies/forwards/mirrors/repeats this type of traffic into the second subnet. Easy on Mac and Linux using readily available software but not Windows)

To troubleshoot your issue you could try the following:
1. For mDNS to work in a bridged setup the bridge should be a layer 2 bridge which requires your NIC's to operate in promiscuous mode. If they don't, for whatever reason, the bridge will operate in layer 3 mode which doesn't route/forward broadcast and multicast traffic breaking the mDNS, Bonjour etc. type of protocols. You can't easily check in what mode it is running and there's not much you can do but for sure I'd update your NIC drivers so install the latest manafacturer issued device drivers and check again.

2. go back to the previous working state so undo the current bridge configuration and configure the first "primary" NIC connecting to your network like you normally would. Then undo any of the IP configuration of the "secondary" NIC connecting to the mR and just set it to 'obtain an IP address autmatically' and 'Obtain DNS server address automatically'. Then after confirming restored network connectivity for your PC and a reboot just to be sure, re-apply the bridge configuration like detailed here: http://www.windowscentral.com/how-set-an...windows-10 but ignore the suggestions Clipper made on CA about assigning IP addresses to the secondary NIC in a different subnet (they make absolutely no sense!).

3. If step 1&2 don't work you could try the procedure outlined here: http://lifeofageekadmin.com/how-to-manua...-72008-r2/ This will try to force your NIC's into promiscuous mode. Just ignore this being about Windows Server 2008 R2. These settings are available on Windows 10 as well (I tried them in an attempt to troubleshoot the upload throughput issues).

Good luck!

edit: I have confirmed Airplay/Shairport works in my setup so NAA should too but I have no ways to test it (NAA) as I don't own the HQPlayer software and don't want to trial it at this moment (one can only trial it once, at least officially so I want to safe that option for later).
Also I'll keep searching and experimenting for a solution of the troughput issue until I run out of options. If I find a solution I'll share it here.

Hi Antonie,

I realize that some water has flown under the bridge (not the network one ) since this post, but thought I should report back to close the loop.

Since the upgrade of Roon to 1.3, I have tried numerous constellations of using the mR as a Roon Ready device with Roon upsampling versus the mR as an NAA device while upsampling via HQPlayer. For me, the later has turned out to be clearly the preferred choice. In particular when connecting the mR directly to my music pc in bridged mode.

In reference to your suggestions above, I did have to do a bit of tweaking before it really worked right with my system. Firstly, the mR will not be recognized as an NAA by HQplayer if one does not assign an IP Address in a seperate subnet to the 2nd NIC as proposed by Clipper in the CA Forum. Secondly, enabling promiscuous mode on my USB to Ethernet adapter had no effect when attempting to improve the overall throughput of the system. What surprisingly fixed the throughput issue was just adding my on-board Wifi controller to the bridge in a disconnected state. This was also recommended by another member in the CA Forum. For me this last step made absolutely no sense, but worked! Throughput is back to normal and the sound is sooooo good.

This tweak together with the HQPlayer and mR in my system has really done something magical. Honestly, one of the top five changes I believe to  have made in my setup to-date.

BB

PS: Ditched my Cisco Switch and picked up a Netgear. Life is easier now...