Speak of the devil, this morning I got a follow-up email from the dealer that sold me it asking how I was getting along with it so I’ve let him know of the issues. Let’s see if he comes back with anything.
There was an issue with the ND5XS2 (which my Naim dealer managed to reproduce on his own unit as well as mine), where it would go into ‘sleep mode’ if this was set in the app, even if playing.
This occurred on the digital out when using an off-system DAC, not with the analogue out (on-system DAC).
It needed a factory reset to wake it up again.
This may not apply to this case, and the firmware releases may have fixed this bug from mid-2019.
Not applicable in this case, none of the digital inputs or outputs are in use and the streamer is connected to the amp with a standard Naim DIN interconnect. Firmware is also on the current production version.
Thanks for your suggestions. I haven’t had a chance to change the router yet. What I did do is setup Bubblesoft on my server with Qobuz and transcoded it to wav. I used Linn Kazoo as the client on both windows and iOS. After about 24 hours it has not lost it once from either controller app. It also sounds excellent. I will be cancelling Tidal and going with Qobuz. The ND5 is showing full bitrate being played. Since I primarily stream, this will probably be my solution.
If anyone is using a last gen Naim streamer, I highly recommend going this route. The Naim app isn’t running as high quality if you are using that for Tidal.
I still have similar issues with my non-naim streaming solution. When I lose power my streamer can get lost. I will not bore you with the exact details, but I have found that powering everything off for about 10 minutes then powering up from the router out to the device last always works. I usually leave a couple minutes between devices as well.
It seems to happen when DHCP assignes the device a different address from the previous one. I think that some dhcp servers can reserve a specific address for a specific MAC address. This may help although I never did this in my setup.
Hi Simon, thanks for your comment in this thread, they have helped me track down a problem with the app “not seeing” my new NDX2.
The NDX was working normally for around 3 day then late Friday night the network “fell over” and numerous devices were not working when I restarted the router & velop mesh network (bridge mode). By disabling IPV6 I have managed to get everything working except the NDX which is hard wired.
After reading your posts I did some investigation & discovered that the NDX2 had been assigned an out of range IP address i.e. 169.254.5.245 (normal range 192.168.x.x), this certainly explains why the Naim App can’t locate the streamer while in a different subnet.
I next tried setup with Wi-fi access, and an in range IP address auto-allocated by DHCP, and the app identified the streamer everything then worked!
I’m now trying to figure out how the out of range IP is being allocated. Factory resets haven’t helped and the NDX gets reassigned the out of range address every time the ethernet cable is connected. Any suggestions would be most welcome.
Thanks in advance.
I found that messing around with IP addresses is best left for the IT specialists.
My BT SH2 DHCP program does it all.
An IP address in the range 169.254.x.x means that your NDX2 can’t see your network and so is assigning itself an automatic address in that range. If it were me, I would probably try a factory reset of the NDX2 next. But @Simon-in-Suffolk If he is around understands this stuff better than I do.
Best
David
Thanks David,
I’ve done around 4 factory resets while attempting a fix, so far with little success 
Have you been able to confirm that the ethernet cable you have plugged in to the NDX2 is actually carrying a signal? Seems odd that wifi works but ethernet doesn’t.
Ok, that is an auto assigned address, ie the NDX2 has given it itself, as it got presumably no response from theDHCP server.
So for some reason the NDX2 is timing out with your DHCP server…are your sure the Ethernet lead is connected correctly and has come up properly?
Actually enabling ipv6 might help layer 2 stay open even if you are using IPv4…
Replaced the cable, same result.
if another device behaves on the end of that ethernet cable instead of the NDX2, and powers with DHCP (such as a lap top or similar) - I am afraid it then looks like your NDX2 and might need to contact your dealer
There is a possibility that there is an interworking issue between your NDX2 and and your DHCP server - but that would be unusual.
BTW what switch are you using? If using A cisco 2960 or similar do try and remove it and see if that helps … it is also possible the loop protection algorithm is confusing your DHCP server and NDX2 flow
Can you test that cable with another device? It might be a problem at the other end of the cable. By that I mean leave the cable where it is and instead of the streamer at the end of it try another device
Thanks Simon,
I have discovered an intermittent feed between my two main Ethernet sockets! DC tests are ok but data is definitely complaining.
I have yet to find the problem but 30 metres of jumper cable has proved it. I have been chasing Ghosts for a couple of days, the solution is finally in sight.
Cheers,
Paul
Hi Simon,
It transpired that there was an intermittent physical Ethernet connection (disconnection) at the wall socket which happened frequently enough to cause my headaches.
An automatic dc pair scan across the link tested OK but eventually I noticed the port LED would occasionally extinguish for a few minutes!
There was no visible physical problem but after re-terminating the cable and reassembling everything sprang into life again.
It’s not always the app but why, oh why, does this happen when a new piece of kit arrives?
Thanks for your contribution.
Paul
1 Like
Glad you are now sorted…
1 Like
Sorry to come across facetious, but I’ve had the ND5 XS2 for at least 7 months plus and haven’t had a single issue with it
My router isn’t too close to the ND5, so bought longer length of Ethernet cable and an Ethernet extender so hardwired from the outset.
I use an iPad and android handset up until last week, now reverted back to an iOS device and runs smoothly. If I’m being honest I had a few issues with Android handset but bar that nothing so please don’t be put off.
It’s a fantastic streamer.
2 Likes
Network issues can really dog any product. Personally I like when I can assign a static IP address. It really drives me crazy when I finally get time to listen and network issues deny that opportunity.
Did I read right that the ND series does not allow or like a static assigned address?
You can assign static ip addresses & they work fine but that won’t necessarily overcome Network issues.
1 Like