UnitiLite does not sustain a network connection

I would temporarily try a different wifi access point to see if the behaviour repeats. If it does take your Naim back to your dealer for checking, if not there may be some sort of wifi incompatibility with your original router.

if it's the latter on your original router try forcing a 803.11 b/g/n connection, and / or changing the physical location to change its MiMo performance.

Simon

+1 ........ Plus Naim streamers are 2.4GHz

Mike-B posted:

+1 ........ Plus Naim streamers are 2.4GHz

......but only when they are in the right mood. Better to turn off the WiFi and use a wired connection.

If your UnitLite is so close to the router just connect it by a natwork cable. That is the prefered route.

ChrisSU posted:

Mike-B posted:

+1 ........ Plus Naim streamers are 2.4GHz

......but only when they are in the right mood. Better to turn off the WiFi and use a wired connection.

Well yes, but I thought that didn't need saying, or should I say didn't need repeating again & again 

Hi There,

I am experiencing the same problem. But for me wiring the network access is not an option.

Now I am considering to fix the network adress for the Uniti 2. Has anybody in this forum experience with this solution?

thx for your reply��

Unless you are a network specialist, I would strongly encourge you to use DHCP. It is designed to make domestic connections hassle free.

In my experience connection dropouts are mostly on the network / router side. 

And if you were a network specialist you would be using DHCP for edge hosts. DHCP is for industry - domestic setups get the same benefits as an added bonus

Thank you for your answer.

I've tried that, because that's the fasted way to install the Uniti. But it didn't work out right for me. Because everytime I wanted to listen to music from the network  (iRadio & NAS), I had to start the set up procedure all over again. Quite annoying.

I'm sorry to say; the Uniti is the only WiFi device with this problem.

I once set a fixed IP address for my server (not streamer) when I was having connection issues and it seemed to help stability quite a bit. All I did was allocate it an IP address on my router/DHCP server. It's simple to do, and just as simple to undo if it doesn't help, so there's no harm in giving it a try. 

Edsel, I only fixed the IP address for my server (Unitiserve) and things improved, although that could have been coincidence! Other forum members have fixed their server IP address too. Again, no harm in using trial and error here. However, I then changed to a fully wired network, which improved everything, and at the same time I reverted to DHCP.

I have this problem intermittently on my wired connection - nothing else on the network suffers from this and it doesn't always happen. The network is correctly set up and I have tried fixed and DCHP IP addressing, neither of which helped.  I just assume that Naim's network connection protocol is a bit crap. I started a thread on this a few months ago and it seems it is not uncommon.

I'd send my SU back to Naim for checking if it wasn't for the ridiculous hassle and delay that involves.

PEV - in most instances the 'fault' is on the network side. There is nothing wrong with the Naim products design as such. 

I would encourage you to reset everything to a known state (i.e. factory setting)  and start over.

I've managed to set up a NAS, UnitiServe, multiple access points and 4 Naim streamers all on my own. And I don't even remeber what DHCP stands for

Adam

Pev posted:

I have this problem intermittently on my wired connection - nothing else on the network suffers from this and it doesn't always happen. The network is correctly set up and I have tried fixed and DCHP IP addressing, neither of which helped.  I just assume that Naim's network connection protocol is a bit crap. I started a thread on this a few months ago and it seems it is not uncommon.

I'd send my SU back to Naim for checking if it wasn't for the ridiculous hassle and delay that involves.

Like Adam, I have four streamers (including a SU) and a Unitiserve and Synology NAS that just look after themselves with DHCP, all wired.  I never have any problems. There is nothing wrong with Naim's network protocol, in my opinion Your issues are almost certainly down to your network, which probably means your router.  Did you try changing it for another?

best

David

As David wrote - most likely a router and how it assigns IP addresses. I found Apple ones to be very stable - my wired and wireless network is defined by a Time Capsule and extended by an Airport Extreme.

Thanks for the input, everyone.  A few points- the router has 5 and 2.4 GHz networks. Most do. The Unitilite is on the 2.4 GHz network. I am using the DHCP default. I can try assigning an IP address from my router console, but I don't really want to become a network admin.  As far as the problem being the network- can't really buy that. I know the network I have- it is sound. No other devices that have used it- 3 different PC laptops, an IMac, assorted phones and tablets- have had this problem.

Will use wired connection when it's convenient to convert. That seems to be the best course from what I'm reading.

Thanks again!

Thanks for the well meant advice  - over the time I have had this problem I have changed every component in the network including modems routers and switches. Oh - and I taught computing at University for over 20 years and I have a PhD in Information Systems - there is nothing wrong with my network! 

As I said above, a thread on this topic revealed that a lot of people suffer with this - it's inconvenient but not as inconvenient as Naim's repair service. The OP seems to have a more severe problem that I do as mine only loses the network every week or two and never drops out when playing. The point of my reply was that whilst wired is better than wireless, going wired may well not be a cure for the OP's problem.

Ages ago now, I suffered a similar issue with a v1 UnitiQute: things would work perfectly on the wireless network (UPnP, Internet radio) until the network connection would just evaporate and the solution was to launch the "search for networks" dance to re-connect. Unfortunately the solution to my situation - which included several other forum users at the time - came in a firmware upgrade also from the dim past. In my case, the symptoms got progressively worse and eventually included lost connections with wired Ethernet and, iirc, the IR handset. I was doing full power cycle and reset to factory manoeuvres way too often. New firmware was the answer. No changes to the network, the router, the DHCP settings, or whatever made any difference whatsoever.

Even now, with years of stability and trouble-free operation under my belt, I still use an Apple Airport Express as a wifi bridge to maintain stability rather than relying on the internal Naim wifi adapter. Sorry this isn't necessarily a solution (unless you find yourself on old firmware and can update!) but it is confirmation that not everyone believes comments and advice like "oh your network or your computer skills or anything other than the Naim wifi is to blame". Sure there are sometimes issues, and sure the workarounds are not always satisfying, and (equally) sure Naim are in a continuous improvement mode, but that context of others doesn't point to a way forward for you (nor does unintentional challenges to your interpretation of the situation). Dropping a perfectly functioning network connection and failing to re-connect is unlikely to be a DHCP issue, a wireless signal issue or whatever. Commiserations. For sure try the wired connection (I ran a wire across the floor to see if a more permanent installation would be worthwhile). Maybe try a wireless bridge to eliminate the Naim adapter if pulling a cable and hiding it is too much hassle. But if neither of those works, get in touch with Naim support, because maybe something internal has made its way into a bad error state and reflashing the firmware (even on the same version) and doing a full factory reset might be the best - or the only - way out of your box. 

Regards alan