ND5 XS, 4.6 and memorizing a wireless network connection

Is your DHCP server set to renew leases after a rather short time? If so, you can probably set it to a longer time if that helps. That doesn’t explain why your streamer is losing its connection, though, as the server should give it a new lease whenever it requires one. 

I doubt very much the ND5 forgets the network,  & more so that its caused by the 4.6 update.    It might be the app loosing something with network discovery so I would delete the app,  power cycle the iPad/Tablet & reinstall the app.      Next is it might be as you suggest that the router is assigning a new IP address,  but why it would do that I have no idea.  All the routers I've had,  & most all the time they were all set to DHCP,   keep the same IP address,  including after a long time switched off when I'm away. If it is assigning all new IP addresses you might need to look at a router problem,  but before that I would go for a system power cycle if you've not done that already. Power all the system off & leave it off for at least 5 mins so your ISP knows you are offline.  First & all one at a time,  turn on the router & let it finish its startup,   next the network switch if you have one,  then the NAS,  then ND5 & finally the app..

Mike, the information of the ND5XS in the menu's shows it is attached to the network (it knows the name, the SID of the network), but it clearly states 'no connection'.

OK,  for some reason the ND5 & router have lost the previously established connection,  like I said in my post,  its not the ND5 that 'forgets'  its the router thats changed something & its probably got some bad/incorrect/confusion links & it needs to be refreshed.   The the total system power cycle as per my post does that,  have you done it yet.  

Firmware 4.6 certainly introduced a new problem in network discovery. I have seen something a bit different to what you report, but it's in the same ballpark which is that if I reboot the router without also rebooting my streamers, they become unconnectable as their leases expire. My Qb and Core always stay connected but my four streamers with 4.6 don't, whereas when they were on 4.3 and 4.4 they always stayed connected.

So I think it's certainly a bug in the 4.6 firmware and it would help get it fixed if you reported it to Naim using the feedback facility in the app.

best

David

Hi, we shouldn’t confuse application discovery with network connectivity... when your issue occurs can you ping your streamer or scan your local network and see it? If not your streamer may have disconnected itself from the wireless LAN... due to some sort of association probe error/incompatibility with your Wifi access point .. if the streamer becomes disconnected the DHCP won’t then work either to renew, or there is an issue with the dhcp flow and the router releases the streamer from its pool. This is most likely a Naim bug.. certainly if working with previous firmware. A temp work around might be to use Ethernet instead, or use a different Wifi access point.

If you can ping your streamer, or see it when you scan your network, then it’s not a network connectivity issue. However if not visible from your Naim app despite being connected to your network (ping or scan) then it points to an application discovery fault. There are many causes for this and Android apps seem to be worse than iOS apps. One thing you can try and do here is look for a setting on your Wifi router called ‘IGMP snooping’ and disable it. Not ideal but can address an application discovery interoperability issue.

BTW I use Net Analyzer on iOS to do a local network/subnet scan... I think it’s free... well worth it... helps you a little when this sort of thing happens 

As per my previous post, it happens with ethernet too. It's not a wifi-specific thing.

best

David

Simon-in-Suffolk posted:

BTW I use Net Analyzer on iOS to do a local network/subnet scan... I think it’s free... well worth it... helps you a little when this sort of thing happens 

Yes, Net Analyzer is a handy little app. I'm pretty sure you really need the paid version, as mentioned by Phil Harris, but it only costs a few quid.

https://forums.naimaudio.com/t...pnp-discovery-issues

Yup the Network Analyzer Lite is the freebee version & its pretty useless.     The best freebee is Fing

I'm waiting for the moment it happens again to do some pinging and taking photos of what the display says in the network settings and contact Naim.

It worked without a hitch with the previous firmware, same router (Apple Aiport, the last version they produced)

Definitely a bug and a quite annoying one too, if you have a really flaky router like the Virgin Media Superhub 2ac which I have and which has to be rebooted at random intervals to get the 2.4 GHz wifi working again. With 4.3 and 4.4 I could reboot it and that was that. But with 4.6 I have to restart anything running that firmware. Things that don't run 4.6 (Core, Qb and everything else not made by Naim) are fine and don't need restarting.

best

David

David, SsSshhhhh, mine is behaving?

Well Gazza the only thing I allow on the 2.4 GHz  wifi is the Qb, as it can't handle 5GHz wifi unfortunately. Sometime I'll get round to putting a long ethernet cable in, but it's not going to be easy, and then if the 2.4 GHz wifi falls over, I won't know or care!

I do wonder whether there is a problem with my Superhub or all Superhub 2acs.  The 5 GHz just works. It's not interference on the 2.4 GHz band because it's not particularly dense here (eg my iPhone and iPad usually can't see any network other than mine) and I can be sitting right next to the Superhub and the 2.4 GHz wifi won't accept a new connection or send or receive traffic from an existing one until it's rebooted.

But not using the 2.4 GHz wifi seems to stop it crashing... 

best

David

I was just prodding....we had a problem a month ago and the cavalry was coming over the hill to install the newer version with the latency problem. I turned everything off,turned everything back on....and we breathe a sigh of relief.

Definitly a bug. If you try to delete the network settings the streamer gets stuck and you have to do a hard reboot (turn off / turn on). I'll report with Naim.