Connecting, Please wait....
Posted by: ken c on 01 December 2015
everynow and then, i get this situation on my NDS (hard wired into switch) and when that happens, i can select and play a track, on the iPad, but i cant use the iPad nor the NDS remote to select another track. And even though there is a play queue, it doesnt automatically then go to next track.
the only way of getting out of this situation is to re-boot the NDS i have found.
anyone know whats going one here and how i can avoid this?
enjoy
ken
I think this happens when for some reason the IP address of the NDS is lost sight of by the network or the IP address that the NDS thinks it has isn't the one the router thinks it has. Rebooting the NDS means that everything relearns what the IP address should be.
You probably can avoid it by fixing the IP address In the NDS and choose something that is unlikely to be assigned by the router to something else, ie well up the allowable range. You could also fix the IP address at the router end, but how you do that depends on the router.
This problem is more likely to occur in my experience when you have lots of stuff joining and leaving your network, eg kids with multiple devices visiting or computers that are not normally used being booted up. It's not an NDS issue - it happens with all the streamers. The latest firmware update made some changes which may help avoid this issue. I haven't really looked into that but others who answer may well know more....
best
David
+1 on the fixed IP address diagnostic.
I had a similar glitch as described by Ken, for me it seemed to be associated with unreliable phone/broadband connection & dodgy BT hub that caused DHCP numbers to be changed more than normal. I changed my set-up from DHCP to fixed (static) IP addresses for my NDX, NAS & iPad, but selected the fixed number(s) from the BT DHCP lease numbers - the assigned numbers are 65 to 254 & the BT hub allocated numbers at the 65 end first. I selected 200 to 202 & the lost connection problem was solved. (the phone connection & BT hub issues have since also been fixed)
We had similar problems in the past, which were fixed by assigning static IP addresses for the streamer and nas. Like Mike, we chose high numbers within the router's range. If you set it at the router end, you then need to set it within the NDS's front panel menu. Basically you switch DHCP off and then ensure the fixed address is correct. You may also need to change the DNS server address, gateway and Mask (usually 255.255.255.0) but hopefully not.
I have had these and plenty of other network related issues with the HDX in the past and on a weekly or daily basis.
Since I have stopped using Mac n-serve and do only access the HDX from IOS-devices, all of my network issues have not occurred again.
I am not saying, that n-serve is causing problems, I am saying that without n-serve problems are gone.
Best
Chris
........... You may also need to change the DNS server address, gateway and Mask (usually 255.255.255.0) but hopefully not.
All I did was to set the fixed IP numbers against each of the devices MAC addresses in the router & then reboot the devices, that changes each of the IP addresses.
Mike-B posted:+1 on the fixed IP address diagnostic.
I had a similar glitch as described by Ken, for me it seemed to be associated with unreliable phone/broadband connection & dodgy BT hub that caused DHCP numbers to be changed more than normal. I changed my set-up from DHCP to fixed (static) IP addresses for my NDX, NAS & iPad, but selected the fixed number(s) from the BT DHCP lease numbers - the assigned numbers are 65 to 254 & the BT hub allocated numbers at the 65 end first. I selected 200 to 202 & the lost connection problem was solved. (the phone connection & BT hub issues have since also been fixed)
Hi Mike...I may well have this completely wrong, and apologise if I have...but I thought you preferred the DHCP set up, as did quite a few other forum members, especially when using a switch.
Davina