I think it's the TIMEZONE (no Netflix, Hulu, YouTube)

I am supposed to receive a call from WD Tecch support this week for the time issue and the problem with Netflix, Hulu and Leanback. I’ll keep you posted.

For all the people experiencing this problem try this ( it worked for me )at least as a temporary solution as I have to do this every time i power on the box. Go to the screen where you change the time zone, go to the option to check for update on system, when message displays it is up to date go back to the time zone option, reselect your time zone and give it from 1-3 minutes. My date updates every single time. Hope it helps everyone, and of course please WD fix this, to say it is annoying is the least of it.

Thanks for the advice, but that doesn’t work for me, it stays the same. I am still waiting for tech support to get in touch with me. Not holding my breath.

Trying to update time after looking for FW updates also did not work for me. And I still can’t connect to Netflix Hulu or You tube…

To be fair, tech support did try to get in touch with me. I already re-schedule with them.

Has anyone found a solution for this yet??

No, no real solution for this yet. Get in touch with technical support (if they haven’t contacted you already) and open a case. Let them know when is the best time to call you and they’ll do everything they can to help you out.

Has anyone had a resolution to this time problem where it freezes at 12/31/1999 ad stops You-tube and Netflicks from working?  Opened a case, but no word.

Suddenly, I have the same NTP related Netflix/YouTube problem with the WD TV Live Plus (WD device).  I have had it for well over a year and exclusively use it for the awesome SMB client to view media over my LAN and for Netflix.  I have had no serious issues with it until 10/3/2014.  My WD device SW/FW is “up to date” according to the ‘check for updates’ settings option.

The WD device date is stuck at 1999 and I have no changes on my LAN gear where NTP is concerned.  While I have dozens of times reset to factory or soft reset or hard reset, the clock always starts at 4PM in 1999.  Since the start of this WD device issue where YouTube and Netflix stopped working simultaneously with the clock malfunction, I have completely opened all UDP traffic bidirectionally to my WD device IP.  I see traffic matches on my LAN gear which shows several NTP server IP’s being contacted by the WD device on UDP 123 sourced from the WD device in the 32768+ UDP source port range.  Using NMAP I have confirmed that UDP 123 is accessible on the NTP servers being contacted by the WD device, so the issue is not with UDP 123 (NTP) being blocked anywhere between the WD device and the NTP servers.  The date/time sync on the WD device is simply no longer functioning despite all types of reset and wide open access to the Internet.

Long story short, the WD TV LIVE PLUS device has suddenly had an internal failure of it’s time sync and time keep functionality.

If WD remedies this defect / malfunction of my WD device, I will remain a happy customer and continue to recommend their products.  If they do not remedy this situation, then the opposite will happen.  :-)  This type of failure is fail balls.

For those interested, this is the list of servers successfully being contacted by the WD TV LIVE PLUS device after a soft reset:
#sho ip nat trans | i 192.168.0.30

Pro Inside global         Inside local          Outside local         Outside global
udp my.public.ip:32768   192.168.0.30:32768    8.8.8.8:53            8.8.8.8:53
udp my.public.ip:32772   192.168.0.30:32772    4.53.160.75:123       4.53.160.75:123
udp my.public.ip:32772   192.168.0.30:32772    8.8.8.8:53            8.8.8.8:53
udp my.public.ip:32772   192.168.0.30:32772    50.7.64.4:123         50.7.64.4:123
udp my.public.ip:32772   192.168.0.30:32772    66.45.245.238:123     66.45.245.238:123
udp my.public.ip:32772   192.168.0.30:32772    206.51.211.152:123    206.51.211.152:123
udp my.public.ip:32776   192.168.0.30:32776    8.8.8.8:53            8.8.8.8:53

WD support, please help resolve this issue.  It appears to be a software related bug.