SuperUniti - nStream cannot find

Posted by: Hector on 08 May 2012

I have a SuperUniti and Unitiqute and have been having problems with finding the SuperUniti on nStream. I leave both on permanently and I always have to use the remote control (or switch on or off) with the SuperUniti to initially get it to connect to the network and be visible on nStream.  Once connected it is fine for the rest of the evening but then i have the issue the next day.  

 

I've tried restoring factory settings but still having the problem.  Unitiqute has been fine, never any problems.  Anyone else come across this with SU or other streaming products? I'm not sure whether if it is a broader network issue. The SU is in the same room as router and the UQ is next door in another room.

 

Thanks

 

Brian

 

Posted on: 08 May 2012 by Larsg

I have typed in the IP adress of SU under select device in n-stream , turned of auto connection and turned on stay connected.

The ND5XS always auto connected.

Posted on: 08 May 2012 by McGhie
I also tell my router not to change the IPs of any of the devices on my network (inc my NaimUniti and SuperUniti). Until I did this my NU used to lose the network from time-to-time. Cheers Ian
Posted on: 25 May 2012 by pj5

Hi Brian

 

Did you ever get to the bottom of this? My UnitiQute has just started doing the same - dropping the network that is. I have tried giving it it's own IP address (not in the DHCP pool) but the problem persists. I says no network and re-connects when i ask it to. Then it's ok until the next day. 

 

thanks

 

 

 

 

Posted on: 28 May 2012 by pro

Hi Hector,I do have the same problem with my superuniti. Each two or three days, it loses the network untill I restart it or reset it although it's connected directly with the router and with a fixed ip.

But I did not get it, that is, how could you switch on/off the SU with your remote? That is impossible.

Posted on: 28 May 2012 by pro

Another thing, the n-stream is a solid programme. So the defaulter is SU. Well I think so.

Posted on: 28 May 2012 by garyi

What router are you using

Posted on: 29 May 2012 by pj5

I'm using a BT home Hub 3 (the latest one i believe)

 

You got me thinking and I and had another look at the router - it was set to automatic channel selection, so i have changed it to a specific channel. - lets see it that helps

 

p.s. also changed it from b/g/n to b/g only

 

Posted on: 29 May 2012 by garyi

Home hubs are nasty. I recommend you replace it with something decent.

 

At the end of the day home hubs are free, well ok you are paying for it one way or the other but they really are not very good products and it will be your issue not the su.

 

If you choose get an adsl 2+ router. The settings for bt are straight forward you will have a user name and i dont think you need a password or use bt.

 

They wont support you though, hense why i dont use them. I reccomend ukfsn for standard adsl.

Posted on: 29 May 2012 by pj5

Although I agree that the home hub is not the best, I would not describe them as nasty. I have had past problems with both netgear and dlink routers. Even cisco routers sometimes have problems (depending on the make of the dslam in the exchange!)

 

You don't need a password because it identifies you by your phone number.

Posted on: 29 May 2012 by IanG
I have been using a home hub 3 with my ND5XS with no problems at all. As said above, I have set up static IP addresses for my NAS and streamer. N-Stream is set up to stay connected. Job done. Biggest issue I had was getting past my Firewall.
Posted on: 29 May 2012 by pj5

Is it possible that the Uniti doesn't monitor the wifi when it's not being used? Therefore a drop out or channel change is not recognised? I have a WII on the network and in the router logs you can see that it re-associates itself every hour.

 

 

Posted on: 29 May 2012 by garyi

I just find it amusing that people are happy to pay upwards of 3k for a piece of hifi that relies on the network, then settle for the cheapest possible device to deliver that network.

 

But hey good luck, its your problem.

Posted on: 29 May 2012 by IanG
A little unkind garyi. As stated, I use a home hub with no problems at all. It may be inexpensive BUT in my experience it is NOT nasty. The guy is asking for a bit of help and your comments are not constructive.
Posted on: 29 May 2012 by pro

I do use a D-link DIR-855 in a wired config but the symptoms are same.

Posted on: 29 May 2012 by garyi

The home hub is rubbish ian, its lucky you are having luck with it. But a proper router will work wonders. Perhaps the threeis better than the two that preceeded it, wouldnt be hard.

 

I am not being unconstructive, the fact is, these devices need a robust home network. And thats not a homehub. They are rubbish.

Posted on: 29 May 2012 by IanG
Seems strange that this guys UQ is fine with the Home Hub but not the SU. Clearly nasty home hubs are also device selective ! Not sure if this guy is used a wired connection or wifi. My experience has been 100% reliability with my Home Hub and Ethernet over mains adapters. I haven't tried mine on wifi perhaps that's were the issue lies here.
Posted on: 29 May 2012 by McGhie
I use a stock router but it's from O2: The O2 Wireless Box IV, which is a rebadged Thomson SpeedTouch TG587nv2. My SU and server both hang off a switch: a ZyXEL GS-105B 5 port Gigabit Unmanaged Desktop Switch (around £10-20, but unanimous 13x 5* on Amazon). These are connected using Cat6 cable from Belkin, and then using same to the router. I've had 5 months of solid uninterrupted performance from nStream and the SU, fed from the above. I've had longer with the NU. I've done nothing special to set the NU or the SU up - they just work. But, my server and UPnP server are rock solid; everything is wired with Cat6; and my music streaming and playing is isolated from other aspects of my network (including wifi) by a switch. I don't know what part my router plays in this, though I have used it to fix the IPs of all devices on my network (and until I did this my NU used to lose the network). I suspect that where people are having issues, the problem will be upstream of the player. There are lots of things to look at and they should be checked out one at a time. Make sure you've fixed the IPs, are using ethernet cables, try a switch, and if none of those things help then you may need to look at your router or streamer. Cheers Ian
Posted on: 29 May 2012 by garyi

Indeed switches help in my experience not that i own a super uniti.

 

Infact even if the router is turned off everything will keep going for a while, as they have their ips and a way to talk.

Posted on: 01 June 2012 by latecomer
I had issues with my NU being dropped, switching from my home hub to a proper router certainly helped. Though I think it will drop once in a while too. It's like a PC, the invariable reset is needed once in a while.
Posted on: 02 June 2012 by pj5

Well, after changing the parameters in the HH3 and after nearly 4 days i have not had the probelm re-appear. Consequently it appears that the problem probably was due to the HH auto changing channels to get the best operation due to other nearby wirless networks. Devices like the WII and PCs cope with this by re-checking the connection every now and then.  In my location there are 6+ other wireless networks, some of these come and go (as people turn then on/off) and some of them are relatively strong. To solve he problem you need to analyse and understand the problem, and to dismiss a device on cost is just naive, as is to throw money at the problem. The best solution would of course be a wired one - which i will get round to later in the year. 

 

As for switches, these work by having a MAC address table (the serial number of the network card) and associating the MAC address with a port. That way when a packet comes in on one port it can forward it out of the correct port. If it doesn't know the desination MAC address, it forwards it out all ports. Switches work at layer 2 (MAC Layer), routers work at layer 3 (IP Layer). you do not need a router if all your devices are on the same IP subnet (as described by the subnet mask e.g. 255.255.255.0).

 

Actually switches are really only a newer and higher port version of a fast bridge. Originally a bridge would typically only have 2/3 ports and take a whole packet in, and check the contents before forwarding it - this was called store and forward. Faster ones were developed that would 'switch' the packet immediately it had the destination MAC address - these were originally called cut through bridges. With advances in hardware port density increased and much of the switching was done not in software but in asics, also facilities such as VLANs added (basically grouping ports together) and the switch was born!