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

One server won't sync with the Operations Master in a Server 2008R2 environment

We have a Server 2008 R2 network, hosted on Hyper-V (the time synchronisation integration service is NOT selected). There are 12 member servers and 2 DCs, which all synchronise well with the FZMO-Operations Master (which is one of our DCs).
The only server that doesn't sync properly is our SQL server; it's out by about 5 seconds.
I have tried restarting the time service and "w32tm /resync" but while it says that it has completed succesfully, the 5 second delay persists.
However, I have found one difference when I queried it for the time server (w32tm /query /source); it showed the non-Operations Master DC as its source (strangely enough,that DC syncs correctly with the Operations Master).

The w32tm /resync /rediscover command doesn't seem to be changing the source to the Operations Master either.

What do i need to change so that the /rediscover option points to the correct Operations Master?

Any other suggestions please?
0
mark-199
Asked:
mark-199
3 Solutions
 
Nagendra Pratap SinghCommented:
Try

NET TIME \\PDCservername /SET /Y

Lets hope it sticks.
0
 
Sarang TinguriaSr EngineerCommented:
Time service is not so accurate to give you time sync second by second
Its there to help kerberose for authentication you can tolerate time diffrence of about 5 Mins in environment using Windows Time Service

Use below set of commands and set your Time service in domain However Expecting accuracy in seconds are not supported by windows Time
If your DC holds the PDC role if yes run below command from CMD (Run as administrator)

net stop w32time 
w32tm /unregister 
w32tm /register 
net start w32time 
net time /setsntp: 
Net stop w32time & net start w32time 
W32tm /config /manualpeerlist:pool.ntp.org /syncfromflags:manual /reliable:yes /update 
W32tm /resync /rediscover 
net stop w32time & net start w32time  

Open in new window



Run in non PDC DOmain COntrollers


net stop w32time 
w32tm /unregister 
w32tm /register 
net start w32time 
net time /setsntp: 
Net stop w32time & net start w32time 
w32tm /config /syncfromflags:domhier /update 
W32tm /resync /rediscover 
net stop w32time & net start w32time  

Open in new window



Just Copy paste the commands in CMD

After Doing above run
dcdiag /test:advertising 

Open in new window



You may also see blog of MVP Ace for More info
http://msmvps.com/blogs/acefekay/archive/2009/09/18/configuring-the-windows-time-service-for-windows-server.aspx
0
 
ChiefITCommented:
sarang_tinguria:

Synchronizing time is a horrible use of a word.

The way time works is each client machine has a +or- window of 5 minutes (called a phase offset). If your computer is out of time by more than +/- 5 minutes windows time will readjust the time for that one computer. Until that computer is out of the 5 minute window, it will not adjust its time.

Instead of using the term "synchronizing", a more appropriate term would be "convergence".
0
 
mark-199Author Commented:
Thanks everyone for your help.
I followed the first solution and at least that immediately "synchronised" the time.
If it drifts again, I will try the second solution.
That particular server has had a time difference of up to two minutes so I wanted to fix this before it drifted apart from the domain-wide time even further.
All other servers have the same time +/- 1 second.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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