Naim app doesn't connect to NDS anymore

Have you tried stopping and restarting the app?  Double click the home button, find the Naim app and then flick it up to kill the process.  Then start it again.

In the past years I had a couple of issues in this field, let me list the reasons I found...

1. Most often - my iPad switched to the other network in my house

2. General network problem

3. Completely switching of the iPad and reconnect

4. Powering down the nds - have every 4/5 months a problem which only get's solved this way....

hope this helps...

How is the system wired  ???  is it all ethernet or is a section wireless or power-line adaptors 

If ethernet does it include a LAN switch between the NDS & NAS and the router on a branch off the switch.

What wireless router make/model is it 

How is the DHCP system set up ?? - if you have static IP addresses, please revert to all DHCP on everything - that will revert to simple simple designed for home system set up.

Switch everything off & starting from the router, systematically restart & wait for it (& each) to complete its restart process. 

Next NAS,  then NDS,   then switch & finally the app,  I would also delete & re-install the app while yr at it.     

 That's strange,  mine connects in two or three seconds & stays connected

Agree delete & reinstall in the OP case - plus I clear cache(s) every week or so to help stalling.

Seems like you've done quite a bit with TJ and have good advice here (turn off, reboot, etc.).

Sometimes I feel like my router changes and autodiscovery works less well (recent firmware and app betas are big improvements in this area). That said, every once in a while, and more often on iPad than iPhone, the naim app doesn't see my two devices (SuperUniti and UnitiQute). I have had good success by manually adding a room (you need to specify the IP address to find, which is simply the IP address used by your NDS, and say what device lives there, which in your case is an NDS). Sometimes this works quite well -- especially when I know the network is functioning (eg can select internet radio via the handset, or can use spotify app to stream through the naim device).

When autodiscovery comes back on, you'll have two icons for your unit -- the manual one and the automatic one; they are linked and selecting either shows both as highlighted / selected. On my iPad, the connection on restart is very fast, but always goes with the manual room (it shows the name and connects immediately)...and when I go back to the rooms screen, everything is there and selectable. 

I hope this helps you out. Best wishes. 

Regards alan 

Hi Sondek71, unfortunately it does sound like the discovery multicast address on your home LAN is not working too well. That is the special IP address the devices uses to find each other on your home LAN. The issue is that supporting wifi and switches have got to perform properly and at least broadcast the discovery alerts out to all connected devices.. sometimes this does not appear to happen reliably on some consumer equipment... especially if equipment has been dormant for a while. Also unreliable links like noisy / weak power line adapters connections and weak wifi links can 'loose' the discovery queries - which means they might not be seen by connected devices.

You could try using a netgear switch with wired conenctions and hanging an AppleAiirPort Express wifi access point for your iPad  off the switch for increased chance of success. You may get funnies from time to time still but it should be more rare with this setup.

There is an outside chance your NDS has an issue and is slow to respond to the discovery query and so is excluded by the iPad - although I feel this is unlikely...

Simon

I only want to know whether someone else is discovering the same problem as I have or if I am the only one. You can be assured that I did everything I could think of so far: Resetted the network, removed the routers, fixed Ip address and DHCP, wireless and wired connections, restarted I pad, deleted and reinstalled the app, used several iPhones and iPads, used several app versions, used the newest and some beta firmware directly from Naim. 

BTW: The device can be discovered in the network. I can play music on the NDS using my Spotify Premium App.

Here are some screenshots of the iPad discovering the NDS.

I can however not access the music libraries as communication between the app and the NDS gets stuck.

https://www.dropbox.com/s/jgn0...pj/IMG_0088.jpg?dl=0

https://www.dropbox.com/s/qpwd...nx/IMG_0089.jpg?dl=0

https://www.dropbox.com/s/8fe1...pb/IMG_0090.jpg?dl=0

I don't have an NDS, but I read this forum several times a day and I haven't seen anyone else have this problem you describe. So I think you may assume it is just your setup.

I would suggest you follow Simon's suggestion. This is almost certainly going to be a network issue and in my experience network issues like this usually only show up in particular situations while everything else works on the network continues to work just fine.

If your dealer's NDS also shows the same issue then Simon's suggestion of an Apple Airport Express as a wifi access point ( that is in bridge mode) so your iPad can see the NDS with a switch, like the highly recommended  Netgear GS105, to connect all your music kit together and connect back to your router seems to me to be definitely the way to go. This is not a lot of money to spend and if you order on the well known retail site now, you can try it all out on Tuesday or Wednesday.  You really shouldn't need to mess around with fixed IP addresses or entering IP addresses manually etc.  Anyway good luck.

David

I've had loads of weird network problems recently.  I installed a new router/modem and it was a disaster.  It had a DNS problem and nothing would connect to the Internet (except IOS devices which I assume use a different DNS server).  There was a fault on the modem which stopped me from putting in a different DNS server so I reverted back to my old modem and things slowly got better.  Then my Superuniti stopped connecting to the Internet (stopping the time display and Internet radio but App and UPNP connections OK).  I fixed this by turning off DHCP on the device (and then turned it back on later).  My Mu-so then (later) suffered the same problem (not fixed yet).  Reinforcing what others have said, this is most likely to be a network problem.

Sonndeck71, the Apple Bonjour discovery and response algorithm is different from the UPnP discovery and response algorithm. Therefore Bonjour and UPnP will have different response performances.. 

If you run a network scanner (Net Analyzer or similar) on your iPad, can you reliably and consistently see a UPnP response on your NDS and UPnP media server? My earlier suggestion will almost certainly improve things for you if you are not doing that already, unless you have a faulty NDS. Anyway up to you...

Simon

I have now removed the static IP address for the NDS and turned back to DHCP.

And - it works!!

I just don't know why this setup worked for more than 2 years.....anyway. Happy to be back again listening to my music.

Congratulations or whatever is most appropriate. 

I found a number of times with my own & others systems that static IP is a place where something not done exactly right can lead to this kind of problem;  & given how well DHCP works in a small home system, it is the best place to be for most users.   

I have my system set to DHCP for all the units,  but in the wireless router (BT) I have set the NAS, NDX & iPad's MAC addresses to a static (fixed [reserved]) IP address within the BT licence DHCP range numbers. (the BT hub is the DHCP allocation mngr)     

When BT do one of their overnight updates/reboots or when I switch off the wireless when I go away for longer periods, it goes straight to the fixed IP/MAC numbers on restart & all the Naim stuff discovers itself PDQ & no problems.

It's the kind of things I would like to avoid, I just want the kit to play. That's the one drawback from streaming the number of failure points gphave increased and it's sometimes difficult to find the answer to a problem.

anyhow congratulations that it could be fixed...

Yes, to keep thinns reliable and consistent, as I have said many times over the years on this forum please use DHCP. It's put there for your ease of use, bypassing  it is just courting potential issues and reliability problems.

You can always use DHCP to assign pre allocated addresses if you require fixed IP addresses.

Simon