Time on Windows 2008 R2 DC incorrect and wont Resync

Hi Experts,

The time on single our domain controller running Windows Server 2008 R2 SP1 that holds all the FSMO roles has the incorrect time…its running about 3 minutes late and all the client computers have the same time so also incorrect.
If I run this command on the DC: w32tm /resync I get the following error message “The computer did not resync because no time data was available” I have tried to stop the time service, unregister it, re-register it and the restart the service but this made no difference. I have tried temp turning of the firewall on the DC also but still the same.

Any ideas how I can fix this?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Seth SimmonsSr. Systems AdministratorCommented:
is the server configured correctly as a time server and to use external source?


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Will SzymkowskiSenior Solution ArchitectCommented:
Check the Directory Service section in the event viewer and you should see warning messages related to W32time. This means your external time source is not configured and need to be.

Source W32time
Type: Warning
Event ID: 12

kevin1983Author Commented:
I have just tried the run the fixit program to setup Configuring the Windows Time service to use an external time source but dont think this has helped.

NTP server in the registry says: time.windows.com,0x1
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Will SzymkowskiSenior Solution ArchitectCommented:
Do you see any events in the event viewer which point to a time sync issue?
Seth SimmonsSr. Systems AdministratorCommented:
expand 'let me fix it myself' and verify the registry entries

on step 4, i use 2 or 3 servers from ntp.org


you can skip step 6 on the correction settings; i typically leave those at defaults and it works fine
kevin1983Author Commented:
I cant see anything in the directory services event log related to the time service / w32time
kevin1983Author Commented:
I checked all the registry entries steps manually and all looked fine and i made no changes in the registry.
interestingly I just run w32tm /resync on the DC and it said "The command completed sussfully" and the time looks ok now. not sure why its started to work

Will just have to sort out the client next as running the same command on them disaplys the same error I was getting on the DC
kevin1983Author Commented:
Thanks for your help, issue has been resolved. Looks like the fixit utility did the trick. Clients appear to be slowly updating to correct time also. I had to run the re-sync command on some of them or stop and restart the time service.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.