My PDC Emulator's time was off, leading to my entire domain's time being off. Some time ago, I had followed this article, but apparently to no avail: http://support.microsoft.com/kb/816042 I searched again and found another article specific to Server 2008 R2 and followed its instructions by running the following commands: w32tm /stripchart /computer:0.north-america.pool.ntp.org ^verified it is off by over 2 minutes w32tm /config /manualpeerlist:"0.north-america.pool.ntp.org,0x1 1.north-america.pool.ntp.org,0x1 2.north-america.pool.ntp.org,0x1 3.north-america.pool.ntp.org,0x1" /syncfromflags:manual /reliable:yes /update ^set up peers (I believe this did the same thing I had already done in the aforementioned kb article) w32tm /resync ^provided me with a new error to work with, "The computer did not resync because no time data was available." I searched the KB and found this article: http://support.microsoft.com/kb/2493006 I then used a sniffer on our egress device to verify that no traffic was coming from the server on port 123, and subsequently downloaded the hotfix from that site. When I tried to apply the patch, the server said the hotfix doesn't apply. This may be accurate in that I subsequently solved the time synchronization problem, but I am confused by the versioning. It is possible that the kb article just confused me, but it looks to me like I should be running a W32time.dll with a version of 6.1.7601.xxxxx where 6.1.7601.21xxx would be a fixed version. However, I am running 6.1.7600.16385 2009-07-13. I verified that SP1 is installed, and I am now concerned that it may not have updated everything it should. For the record, the reason my server wasn't able to sync time servers was because the Defaut Domain Policy is inherited by domain controllers after the Default Domain Controller Policy on our Windows 2008 AD Domain. I believe this is new and didn't happen on our previous Windows 2000 AD Domain. I remembered this when I found another post on this forum pointing someone toward their Default Domain Policy; I then resolved the aforementioned problem by editing the Default Domain Controller Policy and setting the "Computer Configuration -> Administrative Templates -> System -> Windows Time Service -> Time Providers -> Configure Windows NTP Client" to "Disable" instead of "Not Configured" so that the configuration on my domain controller would function instead of being overridden and causing the server to only use the CMOS clock. It took me longer to realize that this is what I should do considering the fact that "w32tm /query /peers /verbose" showed no peers, but I wanted to post about it in case anyone else had similar issues. Anyway, can anyone tell me if and/or how I should verify the integrity/compatibility of my server considering the version discrepancy I think I see? Thank you, Dustin

Hello, sorry but i can not really follow your descriptions. It is a bit confusing. If you have problems with time in the domain it is important the the PDCEmulator is able to communicate with UDP port 123 over firewalls to the external configured time servers. Additional if the DCs are virtual machines make sure they do NOT use the Integrations services from Hyper-V or VMWare tools, belongs also to the other domain members. By default and without any specific requirements the built-in time sync mechanism is fully sufficient for all members. If you think that your time settings somehow are incorrect then i suggest to start fresh beginning with the PDCEmulator, then the DCs and after this all domain machines, without using any kind of GPO or modifying the registry manual. All required commands to reset and start again are included in: http://msmvps.com/blogs/mweber/archive/2010/06/27/time-configuration-in-a-windows-domain.aspxBest regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Thank you for the link, but as I now have everything working (albeit potentially in a more complicated manner than absolutely necessary), I don't think I'll be changing my time settings. My primary concern now is with the version of W32Time.dll, which appears to be incredibly old compared to what http://support.microsoft.com/kb/2493006 appears to indicate it should be. I am running SP1 on Server 2008 R2, but W32Time.dll is version 6.1.7600.16385, which is a way earlier version than the buggy or fixed versions mentioned at that kb article and doesn't appear to be an SP1 dll. My concern is that SP1 may not have fully and/or properly applied. Dustin

Hi, Glad to hear that the original problem has been resolved. Please feel free that the version of the W32Time.dll is correct. I have checked it on my side, the version of W32Time.dll on Windows 7, Windows 7 SP1, Windows Server 2008 R2, Windows Server 2008 R2 SP 1 are all 6.1.7600.16385. By the way, all my machines are 64 bit. Thanks. NinaPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thank you Nina!