No time on UnitiQute2 after 4.3 firmware update

Posted by: feeling_zen on 06 July 2015

I mentioned this in passing before on another post but the problem is starting to really get on my nerves now.

 

If the UQ2 is on a static IP, it cannot get the time from NTP servers. It alternates between reporting errors on port 123 (which is open) and saying "No network connection" (which it has and can access web radio and UPnP sources).

 

For some stupid reason I cannot fathom, you have to switch it to DHCP (which gets an IP address in the same subnet) for NTP to work. I thought the solution was to get the time, then revert back to the static IP. But noooooo.

 

But of course, every time you switch it off for a long weekend away or lightning storms, it comes back with "No Time" again and am back to having to switch to DHCP after each power on, get the time, and then manually re-input the IP address.

 

Stuck a packet sniffer on the port assigned to the UQ2 on the switch and when in staic IP, there are simply no packets coming out of the box headed towards UDP123.

 

C'mon guys. was testing basic functions in DHCP and then static not in the QA test plan?

Posted on: 07 July 2015 by robgr

Is the GW/DNS server correct?

Posted on: 07 July 2015 by Phil Harris

No problems setting static IP addresses on any of my units here ...I'm going to guess at an invalid setting for either gateway or DNS if it works DHCP but not static?

 

Phil

 

Posted on: 07 July 2015 by feeling_zen

Yup I will fully admit to having a PBKAC.

 

And openly admit to being a qualified network engineer who overlooked the most obvious of obvious. Problem now resolved after correcting DNS.

Posted on: 08 July 2015 by Phil Harris

Well done for sorting it and many brownie-points for actually throwing up your hands and admitting that it was a PICNIC issue...

 

Phil