Network clients time not updating
For details of Windows firewall port settings, click on Figure 1,2 and 3.
Especially those coming with Windows XP or Windows Server 2003, may be (by default) unable to query the time from some NTP servers. standalone server or domain controller), NTP servers may not respond to the type of queries sent by w32time.
Live Update Administrator 2.x may be preferable in: If you configure sites on your network for replication from another site, you can configure content updates (for example, Virus and Spyware Definitions) in the database of the primary site to replicate as part of the database.
In this case, you only need to configure updates on the primary site.
To check it open a Date and Time window (click "time" icon in the lower right corner of the desktop) - Note that w32time service may only be enabled when no other ntp daemon is installed on your system. To check if w32time is running, do the following: go to Control Panel-Services.
Scroll to "Windows Time" feature and check its "Status", which should be on "running".
We've provided a list of the most common causes of NTP time sync troubles.
Check which one applies yours and follow the proposed steps to make time service successful. One reason for NTP synchronisation problems may be a firewall or port filter that is blocking the ports the programs use to communicate (by default UDP port 123).But in the console it is showing an incorrect address which I assume is from the DB. For protection against the latest threats, it is important that antivirus definitions, IPS signatures, and other content is always up-to-date.The Endpoint Protection Manager then uses these definitions to distribute updates to clients.In most Symantec Endpoint Protection (SEP) deployments, the Endpoint Protection Manager will download and distribute materials to all of its Windows clients efficiently.For more information, see How to update content and definitions on the clients and Downloading content from Live Update to the Endpoint Protection Manager.