Some issues streaming from Synology NAS to NDX

Hi Paradox

My NDX with Synology 212j does not have this problem. My NAS goes too sleep when not in use but when selecting tracks via n stream it wakes in seconds, 10 sec maybe. My NDX is set to DHCP and connects to the NAS, static IP, via two switches. so nothing complicated.

Hopefully someone will be along soon with some suggestions.

Graeme

Hi paradox,

no, you're not alone. 

i use an NDX/SN1 fed by a QNAP NAS and Asset uPNP (also playing with minimserver).

the NDX seems to get confused easily and has to be switched off/on every so often. I even had to do that after updating n-stream recently. Go figure.

it is a minor inconvenience, but annoying even so.

i guess the software is still a bit buggy; having worked in IT for years (especially with Microsoft) you just get used to it :/

at at least the reboot time is short

I too have an NDX partnered with a Synology Disk Station DS212+ (model # 4.0-2228). I have had this set up for a year and a half now and I have experienced intermittent problems when trying to access the NAS music library via the NDX UPnP menu or remote control (I don't have an iPad). My NDX is just about to come back after a repair for the display and I asked NAIM to look at the network connectivity to see if anything was awry there. Do you have a fixed IP address assigned to your NAS (and to the NDX)? Could be that the NDX has stored an IP for the NAS that has been reassigned in the meantime and is slow to update this previously assigned IP? Might be a contributing factor, if not the root cause. Would be interested to hear if your issue is solved or improved by assigning fixed IPs.

Kind regards

Andrew

Hi all thanks for the reply. I am on DHCP as my IP provider does not allocate a static IP..is it necessary that I get an ipad to run nstreamer? when you say u on nstream is that making use of an apple product? sorry a bit newbie at networking systems..

The point about a fixed IP address is not about your IP provider -- it's not about whether the IP address the outside world sees for your home is fixed.  Rather, it's about the IP addresses within your home network -- the ones provided by your home router in the 192.168.1.xxx range.

Your home router very likely is not set to provide the same IP address every time to certain hardware within your home.  This can cause problems when the IP address of say your nas changes, but the NDX is still looking for it at its old address.  This may require a reboot of the NDX, but it's not the fault of the NDX! 

The home router settings can be changed to provide a static IP address to any connected device, and is a recommended practice to keep multiple networked devices all talking to each other consistently.

I use an NDX connected to a Unitiserve with the music store on a Synology DS3611XS. I use static IP addresses for the NDX, the Unitiserve and the Synology. I can report I get the same intermittent issues on the NDX exactly as found above (input initialising) yet I can still access the music on the Unitiserve via other streaming clients. It really does seem to be the fault of the NDX. It does not happen all that often but is well documented. Other NDX foibles cured by reboots are an inability to keep up with even CD quality rips and clicks. A simple recycle and it will stream in full 24 bit glory. All connections are wired.

Sorry to hear it Lumos. 

Hi all, some updates with regards to the issue. I have set the NDX not to use DHCP, and assigned a specific IP to it. Generally seems ok, except when the NDX is left to idle for more than a few hours, after which it will drop the server.  When it drop the server (but not the network), my go around is to switch the NDX to another input, then switch back to UPnP.  At this point, it will refresh network, but normally will not be able to detect the server.  I will have to restart the server, then the NDX will pick it up.  The hanging has kind of stopped.  Anybody with this issue though, and any other go around/resolution than to restart the whole system once a day?

Thanks!

Just confirming that when you assigned a static IP address on the NDX you also made a reservation on your router and the reservation was outside its DHCP range. By the way, what was the lease time of your DCHP allocations?

You mention that you assigned a fixed IP to the NDX. Did you do the same for the NAS? That is key issue. 

Great point, I always assign servers with static IP addresses, out of DHCP range and reserved.