Question : How to fix Time on PC not matching network?

This all started with  the New Year.  People are receiving the message "The current time on the computer and the current time on the network are different" and are prevented from logging in.

The simple quick fix is to unplug the LAN cable, sign-in, plug cable back in. This works for a few days then pops up again.

The domain is Active directory on 2003-R2. "Windows Time"  service is not running on anyone's PC because from my understanding this service is only for when you want that pc to be the TimeServer for other PC's on the network.

There are 2 policy entries for Domain Controllers and NO policy settings for PC's in the domain  - Windows Time Service and Time Providers.  
Windows Time Service (Policy setting for Domain Controllers): Enabled  & all settings default
Time Providers (Policy setting for Domain Controllers):
    Enable Windows NTP Client - Enabled (no settings)
    Configure Windows NTP Client - Enabled (NtpServer = time-a.nist.gov, Type = NT5DS
    Enable Windows NTP Server - Enabled (no settings)

Is there a policy that needs to be pushed to all PC's? Do I need policy setting to all PC's "enable windows NTP Client". I thought Active Directly natively sync'd all pc's on domain with the Time Provider on the Domain Controller.

Answer : How to fix Time on PC not matching network?

You really only need the PDC emulator to point to an external source if you are using the NIST servers.

PDC emulator should be NT5DS

You can resync your machine by using w32tm /resync /rediscover

Take a look at tigermatt's great article on time, great info  http://tigermatt.wordpress.com/2009/08/01/windows-time-for-active-directory/

Thanks

Mike