So here's the issue: I set a domain computer to sync time off of the dc. w32tm /config /manualpeerlist:192.168.1.15 /syncfromflags:manual /update or w32tm /config /manualpeerlist:domhier /syncfromflags:manual /update then net stop w32time net start w32time w32tm /resync /rediscover w32tm /stripchart /computer:192.168.1.15 /period:1 I get a 180 second offset. ------------------- Then I do net time %LOGONSERVER% /set /y the time corrects itself to the logon server time (192.168.1.15) then 3 seconds later reverts back to the 180 second offset. Any ideas why this is doing this? NOTE: I also tried this: net time /set /y /SETSNTP:192.168.1.15 192.168.1.15 is our ntp server. Does the exactly same thing. Get corrected, 3 seconds later goes to the 180 second positive offset. if I use the GUI, same thing.

Hello, is the server you run the commands on the PDCEmulator from the domain? "netdom query fsmo" will show you. Or is that another DC in the domain or a member server? Net time is not longer used, within Windows server 2008 use w32tm. That server MUST be configured to either use an external(not domain) time source or use it's own hardware clock, so which option is done from you? According to the used ip address this in the LAN and not the BIOS time setup.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

The server that is having the issue is a domain member, not a DC. I'm making the assumption that once I run: w32tm /config /manualpeerlist:192.168.1.15 /syncfromflags:manual /update then net stop w32time net start w32time w32tm /resync /rediscover That box will be repointed to my external NTP time source (192.168.1.15). It works this way on all my other servers. But, All indications are that it is somehow getting a 180 sec offset. Is there a registry entery that would cause this? The fact that I manually set the time using the GUI and 3 seconds later it reverts back to the 180 offset tells me it's not free running. OR the virtual bios time is not getting set via the gui. Did I mention these are virtual machines? Is it possible that the Hyper-V manager is overriding?

Hello, in the domain the DC having the PDCEmulator is the time source, all other DCs sync with that one and the rest of the domain sync with an available DC. Please run on the problem machine: net stop w32time w32tm /unregister w32tm /register net start w32time After that use: w32tm /config /syncfromflags:domhier /update After that you have to run: net stop w32time net start w32timeBest regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Hi there an extract from http://blogs.technet.com/b/vikasma/archive/2008/07/24/hyper-v-best-practices-quick-tips-2.aspx "Make a determination regarding time synchronization. The decision is either to use the Hyper-V Integration Service for Time Synchronization or not" So to check if hyperv is doing it for you is to open Hyper-V Manager--> Right click the VM --> Settings --> Intergration Services --> Time Syncronisation.

I did that earlier with the same result. BTW, I had to reboot the box between w32tm /unregister and /register. Is that normal? And by the way, if I run w32tm /query /configuration /verbose It say's it's using my requested address OR the domain controller(NT5DS). BTW, The DC is withing milliseconds of the ntp server (using stripchart).