NAD M10 Ethernet Problems After Update
Beantwortet
Hello, my M10 updated to 3.12.13 sometime recently and it will no longer play music without skipping and pausing. I use Roon and it goes nuts - Roon says the device may have hardware issues and is slow or not responding. I tried everything to include disconnecting it from everything and plugging it into the same switch that my Roon server is connected to with a 3 foot Ethernet cable (even tried different cables) - same problem. I tried factory resetting it: same problem.
I finally punted and tried switching it over to wifi and it started working fine. It used to work just fine over ethernet. In fact my 6 other Bluesound devices AND my dCS Rossini all work fine over ethernet but the M10 stopped working properly recently and I believe it has something to do with the recent update(s). I'm not exactly sure when it happened as it's been about 6 weeks since I last used it. But it's very frustrating to have everything else work and not this. Please help!
-
Offizieller Kommentar
Hello Bryan,
If your other Bluesound players work fine over Ethernet and your M10 works correctly on WiFi, I wonder if there was an internal update made to your switch that could be interfering with either Roon's protocols or Bluesound's.
You could try two things:
- Test the M10 with Roon while bypassing the switch (temporarily directly ethernet connect to the router)
- Test the M10 connected to the switch and controlled with the BluOS app
To help narrow down the issue.
Regards,
Sam R. -
The switch didn't get "auto updated" it's a Cisco managed switch that requires I log into smartnet and manually download any FW updates. That and two of my other Bluesound devices (a node 2, and a powernode 2) are both connected to that same switch via ethernet -- and so is my dCS Rossini. It's just so very odd. I also tried streaming directly from the Bluesound app (Tidal and Qobuz - both 16 and 24 bit had the same result - it would play for a few seconds then stop).
0 -
I have the exact symptoms but on a NAD C658 since the last firmware update.
Did you manage to fix this issue?
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
3 Kommentare