Help ! UPNP server (UnitiServe) not getting detected by ND5 XS
Posted by: amwarren13 on 06 September 2014
Hello all,
Need some help from the experts please.
Just recently (and has not happened before), my ND5 XS, which is connected to an XP5 XS and situated in a loft conversion cannot seem to pick up the Unitiserve, and keeps coming up with the message <no server>, after trying in vain to search for it.
I have a Uniti and a UnitiQute in other rooms which are connecting to the server without any issue.
I am using Netgear Powerline to connect ethernet.
I have tried resetting the factory settings on the ND5 XS, but still no joy.
Has anyone got any other suggestions please ?
Many thanks in advance.
Ashley.
When that occasionally happens with my SU / US, I do the old power down / restart trick.
Maybe try closing down any iPads/iPods that might be connected to nStream and power those devices down too.
Hopefully that will clear it.
Fingers crossed. Good luck!
Before you power down, reboot your wifi/internet router. That will usually do the trick.
Hi network discovery requires a network method called multicast to discover items. however some cheap network substitutes and devices don't properly support network protocols in certain environments.
So assuming you have some basic connectivity over your link (you can browse web, ping a device on your LAN etc), and you powered down and powered up everything at least once, your powerlines may be preventing your network from working properly.
Temporarily try a wired proper Ethernet connection to see if it all jumps back into life..
if not, then look at your NAS/UPnP server to make sure it's properly advertising it's addresses. Check there is no firewall, and you have only one UPnP server running on one device at a time. If still no good try an alternate UPnP server.
Simon
Tell me more, I don't have issues with connections other than an occasional slow searching for no explainable reason. I had it powered down for 2 days & on power up yesterday & it took some annoying time faffing around to get all the bits talking to each other. This might be worth a try.
Can I "fix" the IP to the same numbers already allocated by the router DHCP
What part of the network - NDX - NAS - iPad - needs to have its IP fixed
& are the "fixed" settings only done at the router - do I leave NDX on DHCP
Ok thanks guys - some things to be getting on with - will let you know if I manage to get things going again.
Ashley.
What I did was:
• Turn off ALL my Wifi devices (router, phones, printer, etc)
• Turn on my router
• Turn on a computer and connect it by ethernet.
• Access the router settings by typing its ip address into a browser
• Turn on my Unitiserve and allocate it a static ip address (I used the lowest number from the available range)
• turn on all other wifi devices one by one, waiting for each one to receive an ip address from the router, (which is the DHCP server responsible for this) before starting the next.
Hope this helps, if you're still in the dark you probably need advice from someone who knows more than I do!
Regards, Chris
Thanks Chris, I will try per your post - but not today - too busy with F1, bowls & eating out.
I am OK with this kinda stuff, but am far far away from knowing what I'm doing & I list everything I change so I have "revert to previous" when it all goes wrong.
But after further checking this morning I find the nStream is the part that has the delay & it is only set to the NDX IP address, not the NAS.
Anyhow thanks for the tips, will get to it Monday,
Chris - one last question - and excuse my stupidity in advance - but how do you allocate the UnitiServe a static ip address ?
The router will have an ip address, which is a long number usually starting 192........... You might find this in its instructions, or phone your ISP tech support. Type this number into a web browser (do not type www. in front of it!)
This should take you to the router settings, where you may need to select an 'advanced' tab, and look for LAN settings.
Somewhere in there you should find the option to allocate dynamic or static ip addresses for your devices.
You may need to know the MAC address of your Unitiserve, which you will probably find written on its back panel.
Good luck!
Chris
Many thanks for your help Chris. much appreciated.
Ashley.
I have fixed NDX, NAS & iPad to static IP address on the BT HH4
I will see how it goes, so far it seems to be OK, maybe my imagination but it seems to be a bit quicker connecting
Can someone advise if any advantage in also fixing the individual items to static as well.
I did consider setting a static address for my streamer, and maybe other devices too, just to see if it helped. For example, I wondered if n-stream on my iphone would have a faster, more reliable connection to my Superuniti if that had a static address. However, this is not something I have yet got round to trying out. There are other, more technically knowledgable contributors to this forum than me who may be able to offer further advice. (You know who you are, guys.......)
I will leave mine as it is Chris - NDX NAS & iPad on static IP - then see how it goes. I intend to do a complete system & router power down tomorrow & see how it all hooks up again, as that was my problem last week.
Meanwhile if some expert advice says to do something else, great
Chris - one last question - and excuse my stupidity in advance - but how do you allocate the UnitiServe a static ip address ?
You need to download the Set IP tool from the Naim website.
You need to set the IP in the server, and also in the Serve itself. Eg, my serve is set as .......140 at the router end. You then use the tool to set the IP, DNS gateway etc at the Serve end. It's actually really easy to do. The tool's blurb tells you how.
I met my local IT geek last evening it he advises best for me with a small network to leave it to DHCP. But NAS on static is OK & will help speed & search. So thats what I've done
nStream took its time to find the NAS eventually saying it could not find it
I cleared both caches & its all found & ready to go
Seems snappy & maybe faster than before, but maybe I'm kidding myself.
I think thats it, I'm done - I hope
Conclusion after 2 days is that it is more positive connecting to NAS & faster scrolling thru nStream & starting play. The only delay is on initial start-up when the NAS is waking up from hibernation, but that is just a few seconds & does not result in unable to find anything.
I have re-set the NAS IP Address in the router (BT HH4) to static.
Rebooted the NAS & it hooked up automatically to the new number, then re-set the NAS itself to static IP on the new number
I did not go outside the BT LAN IP range, I only have a few items on the network so I don't expect any conflict. I just added a 3rd digit to the DHCP allocated number e.g.192.168.1.67 to 192.168.1.167
Also yesterday BT made a managed change & reboot of the HH4 (no idea why) but I was pleased to see the static IP worked OK after. I later turned all the units & the router off & went thru a sequenced & staged restart starting from the router & its all connected & working fine.
You need to set the IP in the server, and also in the Serve itself. Eg, my serve is set as .......140 at the router end. You then use the tool to set the IP, DNS gateway etc at the Serve end. It's actually really easy to do. The tool's blurb tells you how.
HH, having solved my US/SU connectivity problems (touch wood) by setting a static ip address for the US, I'm still curious about how and why I might need to use the tool. I've downloaded the tool, but it's just a .msi file, whatever that is! If you try to download the instrucuions from the US web page, you get an HDX instruction manual!!!
If I had any sense I'd just forget the whole thing (if it ain't bust, don't fix it!) - but I'm just curious.
Regards, Chris
Chris the instructions for the uServe are the same as for the HDX. This has led to some confusion in the past.
Hi Bart, I assumed that would be the case, but the instructions you download are for the HDX desktop client only, and make no mention whatsoever of the set ip tool.