We have a similar issue with the 4310 (5.2.3) where 1 in 4 reboots result in the DMP not getting the date / time from NTP. Solution is typically to reboot and hope it catches the correct time on next load. The reason the clock is off in both hours and minutes is because when NTP is not successful the default date time is Dec 31st 1999 0:00am. You can always do a test to see if the year is below 2011 and if so deal with the issue by either a) rebooting or b) trying to force NTP to run again.

Hope the above helps.

From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Friday, 21 October, 2011 2:26 AM
To: cdicuser@developer.cisco.com
Subject: New Message from Michael Velasquez in Digital Media Suite API - Digital Signs API Forum: NTP not working on DMP 4400 v5.2.2

Michael Velasquez has created a new message in the forum "Digital Signs API Forum":

--------------------------------------------------------------
We have several Cisco DMP 4400's with firmware 5.2.2 installed at one of our client locations. They are displaying an html that has a date and time clock built in Adobe Flash and it is not showing the correct time. We enabled NTP on the DMP and set the correct US Central time zone, which works at another client showing a similar Flash based clock (same actionscript) and also in our office. That other client and our office DMP are 4400 running firmware 5.2. We suspected that the problem client's firewall was blocking access to pool.ntp.org<http://pool.ntp.org/> but their IT tells me this is not the case. Strangely, the time being displayed is not an even hour off when we change the NTP time zone. It will show several hours and minutes off the expected time. For example if it's 10am PST and we set it to EST it will show 12:13pm the next day. Can you please offer any suggestions? Thank you.
--
To respond to this post, please click the following link:

<http://developer.cisco.com/web/dms/forums/-/message_boards/view_message/4629956>

or simply reply to this email.

While this isn¿t a fix, to confirm that the system time is in fact incorrect you can enter the following link in a browser:

https://<DMP_IP_ADDRESS>:7777/get_param?p=sinfo.time

If this time is correct, then there is an error in their application somewhere. Otherwise it is probably DMP related.
 
-Hashir

Michael,
 
I just tried this on a DMP 4400 running 5.2.2 and I am having no problems. You should see some text at the top left of your browser. It isn't particularly apparent (although it isn't hidden by any means either), perhaps you are just missing it?
 
Could you paste a screenshot by any chance?