NStream only finding one of either Superuniti or UnitiQute - suggestions ?
Posted by: jobseeker on 11 January 2013
I just wondered if any network experts had any comment on this problem.
I have a Superuniti and UnitiQute in different rooms. The network is provided by a BT Homehub3 in the same room as the 'Qute. A gigabit switch is connected to the gigabit port of the router, with one of the switch ports feeding a similar switch in another room where the Superuniti is situated. There are other devices connected to the switches (Sky receivers, TV's, BR player, Vortexbox etc). There are also computers connected wirelessly to the Homehub3's wireless network.
For some reason, when I open NStream on iPhone5 or iPad (IOS 6.0.2) there is often only one of the Naim devices shown. On such an occasion, it is always the one which was last connected to by the iPhone or iPad. If I disable 'auto connection,' then enter the IP address of the other Naim device, Nstream connects to it. If I then re-enable 'auto connection', both devices are shown like they should be and I can swap between them. However, whichever one is not currently connected to by NStream will often have disappeared again when I next launch NStream. On one occasion, it disappeared whilst I was actually looking at both devices in the 'settings' screen. I seem to have a similar problem when using an app on the iPhone / iPad to control a Revo K2 internet radio/streaming device, in that the control application frequently can't find the device. A reboot of the router does seem to temporarily effect a cure in that the devices can be found as expected, but the problems usually reoccur when the respective app is re-launched.
The router is using DHCP, but is set so that every device on the network has a reserved IP address in the router. All show up ok if I interrogate the router to see what is connected to it. Everything on the system works fine, whether hard-wired or connected via wireless. It is only when using the iPhone/iPad for wireless control of these devices through the network that the problem occurs. Nothing has been changed in settings and no new cabling or devices have been added. The problem has just 'appeared' from nowhere.
I'm suspecting a wireless issue somehow, but I'm no expert in these things. Can anyone offer any suggestions ?
Posted on: 11 January 2013 by garyi
Personally I would set the IP of the devices outside of the DHCP range on the units themselves. Not reserving via the router.
Posted on: 11 January 2013 by jobseeker
What does that achieve ? (I don't understand these things)
Posted on: 11 January 2013 by garyi
Not meaning to sound like a ****, but if you don't understand then you might land up in more bother than currently.
Certainly have a look about the webs for how to set fixed IPs. In your case it sounds a bit like an IP conflict or perhaps there is an issue with nstream, only people with more than one device could confirm your experience.
Posted on: 11 January 2013 by rjstaines
There seems to be a tide of support on this forum for 'fixed IP addresses' and 'don't use DHCP'. But then there are a lot of network problems people seem to have... could these two things be related?
Forget fixed IP addresses - set all you network clients (things) to DHCP and let the network DHCP server (usually your router) do what it's good at... managing devices on your network.
Why do I say this? because what you're describing jobseeker is typical IP address conflict symptoms.
"Try that and see what happens" as they sometimes say in Salisbury.
Posted on: 11 January 2013 by jobseeker
The ip addresses are consistent and stable as far as I can see. Both naim devices always have the same address and are found using it within Nstream at any time. The router always has them listed by these addresses. The same is true of all other connected devices. The addresses have never changed.
However, I've noticed that I had the wireless settings set for 40 MHz 300 Mbps dual-channel operation (no networks of consequence clashing channel-wise). I've changed that to the more usually recommended single-channel lower-bandwidth setting.
Since doing this earlier this evening, the problem has not surfaced again yet with either the Naim or Revo devices. I'm cautiously hopeful, though I still don't understand why that would have caused the issue.
Posted on: 11 January 2013 by Simon-in-Suffolk
Hi, it does sound awfully like your wireless is mucking up the upnp multicast discovery frames... This regrettably is not than unusual. I am afraid fixing ip addresses only masks the issue if this is the case and you could have other problems. Can you beg/borrow/steal an Apple Airport express and plug into your switch and use the SSID on that to connect your iPad/iPhone to... I suspect you may find reliability improves. The express supports multicast discovery required for AirPlay and uPnP.
Simon
Posted on: 11 January 2013 by jobseeker
I'll look into that. Thanks for your contributions guys.
Posted on: 12 January 2013 by Forester
Jobseeker,
My set up seems very similar to yours i.e.
BT Homehub 3 > Switch > NAS
> UnitiLite
> Computer
> 2nd switch > SuperUniti
> AV equipment
The only difference is that I do not use the gigabit switch in the Homehub and (touch wood) it works. I do not have the technical knowhow to even understand what a multicast discovery frame is and would never dare to disagree with Simon as he has a proven track record of being very knowledgeable and has helped a lot of people on the Forum. However on a more simplistic level I recall that your SuperUniti went on holiday to Salisbury. Section 2.9.3 of the reference manual refers to potential issues if it has been previously used. Would such a trip equate to that? If so have you tried a simple systems reset as suggested? Apologies if you have already been down that route.
Posted on: 12 January 2013 by Simon-in-Suffolk
Forester, it looks like its with the wifi the discovery frames might be going astray. in your setup do you use the wifi on the BT Homehub?
If so if its the same version that Jobseeker uses it does suggest he shouldn't be having a problem unless his standalone switch is not up to the job which is unlikely..
of course there is the possibility of a bug with the Naim software but i guess we would be seeing more issues.
Simon
Posted on: 12 January 2013 by jobseeker
Originally Posted by Forester:
Jobseeker,
My set up seems very similar to yours i.e.
BT Homehub 3 > Switch > NAS
> UnitiLite
> Computer
> 2nd switch > SuperUniti
> AV equipment
The only difference is that I do not use the gigabit switch in the Homehub and (touch wood) it works. I do not have the technical knowhow to even understand what a multicast discovery frame is and would never dare to disagree with Simon as he has a proven track record of being very knowledgeable and has helped a lot of people on the Forum. However on a more simplistic level I recall that your SuperUniti went on holiday to Salisbury. Section 2.9.3 of the reference manual refers to potential issues if it has been previously used. Would such a trip equate to that? If so have you tried a simple systems reset as suggested? Apologies if you have already been down that route.
Yes, my set-up is very similar to yours. I don't think my issue has been connected with the SU being away for repair, though thanks for the suggestion.
The problem seems to have gone now that I have disabled the wide-bandwidth 40MHz 300Mbps wireless setting in favour of the more standard 144 Mbps setting. I don't know why that would make a difference though. The system has been very stable since it was installed. I had forgotten that I had enabled the wide-bandwith wireless setting, but even so it's been fine using that until the last week or two.
Simon, I've just found an older generation Apple Airport Extreme A1143 model 130 Mbps wireless N router in a cupboard (not the dual-band version). I recovered it from the home of one of my sons when he moved. Would that be worth a try for me ? If so, do I disable wireless on the Homehub, or do I use both ? If both, I presume I would have to set them to use different wireless channels ?
Posted on: 12 January 2013 by Simon-in-Suffolk
yes - give it a try and report back
remember - bridge it - (no double nat etc) and set up a new SSID (wifi name). The device will take care of the rest.. don't worry about channels etc. Check that it has muticast enabled - it is by default, but might have been switched off previously.
for the experiment leave the old homehub wireless alone.
Simon
Posted on: 12 January 2013 by jobseeker
Can you just explain a bit more about "bridge it .. no double nat etc". I'm not too sure on that one 
I think I need some control software from Apple as well ?
Posted on: 12 January 2013 by Simon-in-Suffolk
Hi - yes download the control software from Apple - its free. To be honest the bit about bridge mode will make sense then, as it refers to it in the setup within the control software.
I think the penny will drop then 
Posted on: 12 January 2013 by Forester
Simon, the conversation has now moved on a bit but to answer your earlier question the only thing connected wirelessly is the I-pad. Everything else (now) uses proper patch cables, and inter-room connections end in wall face plates. However visitors have connected their laptops etc wirelessly without any problems.
Posted on: 12 January 2013 by Simon-in-Suffolk
.. And you are using the homehub wireless?
Posted on: 12 January 2013 by jobseeker
Well I've got it set up at a basic level after managing to do a soft reset and change passwords etc. after downloading Airport Utility 5.4.1 to my Windows XP netbook. I have it showing in bridge mode with channel settings on auto. I can't see anything anything in the set up about multicast but I'll keep looking. I'm not sure if there's a newer version of this Airport Utility compatible with 2nd Gen Airport Extreme and Windows XP. If so, maybe there are more set-up options in that.
I'm wondering if it's worth trying the 5Ghz band or if it's best left at 2.4 Ghz. I know the iPad can connect at that but I'm not sure about our 2 iPhone 5's
Posted on: 12 January 2013 by Forester
... And are you using the homehub wireless?
Simon, not sure whether questions have crossed. Either way this will sound very simplistic. Yes I am connecting the I-pad wirelessly to the homehub, as are any visitors. I say that as I am not aware of anything else that they could connect to as there is nothing else in the system. I am afraid this exposes my lack of understanding as I just thought that these connections happened automatically. Therefore I have no idea about changing bandwidths as jobseeker refers to in an earlier post. As an aside I have just remembered that my Canon printer is also connected wirelessly and that just seems to work as well.
Posted on: 12 January 2013 by Simon-in-Suffolk
Jobseeker, I have also just looked at the setup app for my Express, and there is no mention of multicast now so I guess it stays on... Any way it sounds like you have it up and working... Is there an improvement when you connect to the new SSID on the express from your iPad ?
Forester, thanks, no you don't need to enter bandwidths etc, other than security key and SSID name it can be plug and play.
Posted on: 12 January 2013 by jobseeker
I think I'll have to play around a bit before rendering judgement. As I said earlier, the problem has gone away now anyway even with the Homehub3 wireless network, once I'd disabled 300 Mbps high-bandwidth settings. I'm pretty sure Forester will never have been into the Homehub3 settings to have ever enabled that in his set-up, judging by what he says about the subject. I still don't know why that would have cured it though.
Thanks for your advice
Posted on: 13 January 2013 by jobseeker
Simon
I don't you if you'll see this and it may be a stupid question. Which of the ports on the Airport Extreme should be connected to the switch for best results (the first one has a different symbol, which I presume is meant for an ADSL connection ?
Posted on: 13 January 2013 by Simon-in-Suffolk
Hi, I am only familiar with the express, however with the extreme if either port works I doubt it matters.
Simon
Posted on: 13 January 2013 by jobseeker
Well, it's connected to the switch via the WAN port (with the round symbol) rather than any of the LAN ports. I believe the Express ports are similarly marked). I think that may technically be the wrong one. Seems to be working ok though. I have a feeling that maybe in Bridge mode, the WAN port acts as a LAN port anyway.