• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 339
  • Last Modified:

NTP time not snchronised in the server

I have windows server 2008 R2 as my main domain. All of my client’s computer synchronize with the domain server to update time. Gradually and eventually this month our time in client and server were about 3.5 minutes late than the standard time. Followed the following http://support.microsoft.com/kb/816042 and found out it all the settings were right. Even after that my time still did not got updated.
Then I followed the following steps
On the main DC:
d. “W32TM /config /reliable:YES”
e. “W32TM /resync /rediscover”

On all other DCs:
W32TM /resync /rediscover.
It did not updated.
Just wanted to know any ideas to start researching to synchronize to correct time. I used http://tycho.usno.navy.mil/ntp.html document to synchronize.
1 Solution
Will SzymkowskiSenior Solution ArchitectCommented:
The first link you have provided is the correct link to follow. Did you check to ensure that all REG values are the same as the technet?

Also run the following command from your other DC's
w32tm /query /status
This will show you what DC your computers are using for there time server
Note that clients can point to any DC for the correct time but all the DC's should be pointing to the PDC holder.

Also take a look at the following link which will explain in detail how the Time Server works.

Hope this helps!
Nagendra Pratap SinghCommented:
Do you have DCs on a VM?
SteffesITdeptAuthor Commented:
@npsingh123. No the Domain Controller is not in VM.
 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Nagendra Pratap SinghCommented:
I will wait for other experts to comment.
SteffesITdeptAuthor Commented:
@Spec01. I made sure all reg values are as described in the technet. I ran the query
 w32tm /query /status and made sure all DC are pointing to my Parent Domain Controller. I also read the link you provided me in detail and understood how the windows time service works. Now any other solutions/ site should I try to continue on?
Hmm - from my experiences, the W32time service is sometimes a pain in the a** if used with NTP time sources.

My tip would be to just disable W32time on the systems and install a native NTP client, i.e. one of the ports for Windows listed on the ntp.org link page.
SteffesITdeptAuthor Commented:
We found the solution it was because of domain controller settings for time server.
SteffesITdeptAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for SteffesITdept's comment #a39370339

for the following reason:

Found answer
SteffesITdeptAuthor Commented:
This can be closed

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now