Can't get iRadio or Tidal to stream

Posted by: Graham Clarke on 17 October 2015

For iRadio when I click the icon it says "connecting..." but never does and eventually times out.

 

For Tidal, I can see and search for albums/artists/tracks etc via the Naim app, but when I select Play there's a long delay before it says "Can't play" presumably when it times out.

 

I'm using BT Infinity 2 via BT Home hub 4 which has most recent firmware.

 

My NDS is using wired Ethernet to a Netgear 108 switch in my lounge.  It's configured with a fixed IP address (so DHCP disabled).  This in turn is connected to a Netgear 116 hub upstairs my in office.  The 116 hub is connected to the 1 gig port on the Home Hub 4.

 

The HH4 is also enabled for wireless and there is a second wireless network connected to the 108 switch.  However, given everything for music playback is wired this shouldn't be relevant.

 

Playback from my NAS drive (also connected to the 108 switch) is rock solid without any problems.

 

I've also confirmed that there isn't a fault with the NDS as iRadio worked fine on it at UHES.  So I'm suspecting it is a network issue of some description but am stumped where to look next.

 

All suggestions gratefully received!

 

Graham

PS: I did also try emailing Naim via their support address a week ago and didn't even get a reply...

Posted on: 17 October 2015 by David Hendon

Did you reset your NDS to manufacturer's settings after doing the 4.4 firmware update? If not then that is the first thing I would try As Naim recommend this and there have been a few other odd things reported on the NDX which get fixed by a reset. You do that via the spanner button on the remote.

 

Regarding Naim support, I have always found they are excellent on the phone so if you don't get a reply to an email, it's probably worth ringing them, especially if it's a complicated subject where it's much easier to discuss than to conduct a prolonged email exchange.

 

I hope this helps.

 

best

 

David

 

 

Posted on: 17 October 2015 by David Hendon
Originally Posted by David Hendon:

Did you reset your NDS to manufacturer's settings after doing the 4.4 firmware update? If not then that is the first thing I would try As Naim recommend this and there have been a few other odd things reported on the NDX which get fixed by a reset. You do that via the spanner button on the remote.

 

Regarding Naim support, I have always found they are excellent on the phone so if you don't get a reply to an email, it's probably worth ringing them, especially if it's a complicated subject where it's much easier to discuss than to conduct a prolonged email exchange.

 

I hope this helps.

 

best

 

David

 

 

And another thought, it could be worth trying rebooting your BT home hub just in case the DHCP isn't working properly.  Once you've done that restart your NDS again too.

 

best

 

David

Posted on: 17 October 2015 by Graham Clarke
Originally Posted by David Hendon:
Originally Posted by David Hendon:

Did you reset your NDS to manufacturer's settings after doing the 4.4 firmware update? If not then that is the first thing I would try As Naim recommend this and there have been a few other odd things reported on the NDX which get fixed by a reset. You do that via the spanner button on the remote.

 

Regarding Naim support, I have always found they are excellent on the phone so if you don't get a reply to an email, it's probably worth ringing them, especially if it's a complicated subject where it's much easier to discuss than to conduct a prolonged email exchange.

 

I hope this helps.

 

best

 

David

 

 

And another thought, it could be worth trying rebooting your BT home hub just in case the DHCP isn't working properly.  Once you've done that restart your NDS again too.

 

best

 

David

Thanks David.  Yes, I did do the factory reset after I did the upgrade.  Prior to the upgrade iRadio wasn't working (and still isn't), which makes me think that the issue isn't around the 4.4 firmware.

 

DHCP is disabled for the NDS which uses a fixed IP.  I might try enabling DHCP to see whether it makes a difference.

 

 

Posted on: 17 October 2015 by David Hendon

Did iradio on the NDS ever work with a fixed IP address? And if yes, did it ever work with the BT Home Hub 4? If no, it may be that it is fixed outside the IP range of the router in your BT HH.  Different routers sometimes have different default IP Ranges.  That wouldn't affect the connectivity of your NDS and NAS if both are fixed, but could explain why internet-delivered content doesn't work on your NDS.

 

Anyway I agree that you should try setting your NDS back to DHCP. And then reboot everything again.  DHCP is designed to work in situations like this and you shouldn't be needing to fix the IP address.

 

best

 

David

Posted on: 17 October 2015 by Trevor Wilson

hi, ive poked naim support on this one, they should be in touch if they havent already

 

Trevor

Posted on: 18 October 2015 by Simon-in-Suffolk

Graham, I would re-enable DHCP on your NDS. (For me it's such a bad idea not to use DHCP) You can always reserve its address via DHCP on the router if you need to. 

When you do a network scan can you see the NDS, or does it appear as an attached device on your router once you re-enable DHCP?

if it does, note its address, can you point your web browser at that numeric address? Do you see the NDS internal status screen? if using DHCP you should see things like DNS servers now match the router address or if external match the DNS servers shown on your router online status. Also really importantly, the default gateway should match your router address on your home network.

what has changed? Is it just the new firmware or something else? 

Simon

Posted on: 18 October 2015 by Simon-in-Suffolk

An example...

 

image

 

Here my NDX gets everything via DHCP and my router LAN address is 192.168.1.1 (255.255.255.0)

Posted on: 18 October 2015 by Mike-B

I have similar - my NDX, NAS & iPad have "reserved" (static) IP addresses within DHCP. It seems to be the ideal solution to avoid IP conflict & errors in setting up full fixed IP addresses. 

In my case the BT router has a block of DHCP licence numbers from 064 to 253,  I have reserved the IP numbers far away from the routers first pick 064 end (xxx.xxx.x.200/201/202)  

With more away from home power cycles than most & a string of beta test updates in the last 12 months,  it has never failed to complete full network discovery.

Posted on: 18 October 2015 by Graham Clarke
Originally Posted by David Hendon:

Did iradio on the NDS ever work with a fixed IP address? And if yes, did it ever work with the BT Home Hub 4? If no, it may be that it is fixed outside the IP range of the router in your BT HH.  Different routers sometimes have different default IP Ranges.  That wouldn't affect the connectivity of your NDS and NAS if both are fixed, but could explain why internet-delivered content doesn't work on your NDS.

 

Anyway I agree that you should try setting your NDS back to DHCP. And then reboot everything again.  DHCP is designed to work in situations like this and you shouldn't be needing to fix the IP address.

 

best

 

David

No, iRadio never worked.

 

So as mentioned in an earlier post, I reenabled DHCP (and told me HH4 to always issue the same address) and now both iRadio and TIDAL work!

 

Thank you everyone for your suggestions, it's most appreciated.

 

Graham

 

Posted on: 18 October 2015 by Graham Clarke
Originally Posted by Trevor Wilson:

hi, ive poked naim support on this one, they should be in touch if they havent already

 

Trevor

Thanks Trevor.  Turning on DHCP resolved it, although it's not clear to me why it wouldn't work with a manually assigned IP address.

 

Feel free to unpoke support.  One less thing on their plate to deal with 

Posted on: 18 October 2015 by Simon-in-Suffolk

Graham, glad its working now that you have DHCP correctly re enabled.

Many modern consumer routers need to know about attached devices if they are to manage the data flow to and from the web for both security and quality of service (QoS). Also the device on the network needs to be correctly told the default gateway address and DNS addresses. With out this the device will never be able to escape from the home network. DHCP on the router usually takes care of all this, and it appears it has in your case.. remember keep it simple..... enjoy   

Simon

 

Posted on: 18 October 2015 by David Hendon

Excellent news Graham.  You now have access to far music than you will ever be able to listen to!

best

 

David