NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi unable to update time v1.8.0.6
Hello all, After updating to v1.8.0.6 my orbi has been unable to update its system time. I have tried via Advanced->Security->Schedule to change timezones, check and in check adjusting for DST, wit...
You sound like you know your way around networking. From reading your post, though, it sounds like you used the public IP address of the netgear time server. If so, that would be incorrect.
What you want to do is assign the domain name "time-g.netgear.com" to a local IP address on your LAN, e.g. 192.168.1.10.
If the Orbi GUI would accept it (a big IF) then you would use 192.168.1.10 as the reserved IP address and time-g.netgear.com as the "Device Name".
I just tried this on my network to see if it would work. It took all of abot 10 seconds to alias the domain time-g.netgear.com to my Linux server at 192.168.1.10. The trick works perfectly. If I ping the netgear time server, I get directed to the local Linux host.
ping time-g.netgear.com
Pinging time-g.netgear.com [192.168.1.10] with 32 bytes of data
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64
Reply from 192.168.1.10: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.1.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
That's using my Ubiquiti Edgerouter. The trick should work on many other routers. I just can't easily try it with my Orbi.
You could also setup a separate DNS server on your LAN to accomplish the same thing. That could be a bit of work though.
I have had the same issue with AT&T on all of my Netgear routers. I just use Telnet and issue a date command to fix it manually. It sucks but it works. It is odd because some instances the Orbi will get the correct date/time after a reboot (which is only when I update the firmware).
Telnet command: date -s 2017.03.17-16:11-0800
(Date)-(Time)-(Timezone)
I might have to give st_shaw's recommendation a go.
I reached out to Netgear's twitter account to see if they would pass this concern on to engineering. They told me to create an "idea" topic as that's how they guage customer interest in features/fixes.
If you'd like to "vote" that Netgear fix the NTP problem, please add your comment on the topic here: https://community.netgear.com/t5/Idea-Exchange-For-Home/User-Alternate-NTP-Ports/idi-p/1257017#M670
Thanks for all your help! It's up to Netgear to make this simple change!