Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Windows Server time off by one minute exactly

Posted on 2012-04-04
16
891 Views
Last Modified: 2012-09-24
We have many servers, all of which sync their clocks with one "primary" server (SV1).  

The clock on our Exchange server (SV2) occasionally gets out of sync, typically by 60 seconds exactly.  SV2 is now set to sync every 15 minutes, but this does not seem to help.

SV1 is Window Server 2008 R2
SV2 is Windows Server 2003

This network is not on the Internet, so there is no syncing to public time servers.

Any suggestions?
Thanks
0
Comment
Question by:Rob Rudloff
  • 10
  • 3
  • 2
  • +1
16 Comments
 
LVL 4

Assisted Solution

by:Red_Tech
Red_Tech earned 50 total points
ID: 37806565
I would look in your event log and see if you have any events related to windows time service. Post any errors and event ID's.
0
 
LVL 26

Assisted Solution

by:Leon Fester
Leon Fester earned 50 total points
ID: 37806618
I'm assuming the SV1 is a Domain Controller?
Have you configured SV1 as an authoritative time server?
http://support.microsoft.com/kb/816042

Next configure your GPO for the values of the time source.
See link below for details.

Alternatively if you've manually configured the server time sync settings then check this link:
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_27660502.html

If it's not a domain controller then review the following article/instructions:
http://blogs.msdn.com/b/w32time/archive/2008/04/02/configuring-a-standalone-time-server.aspx
0
 
LVL 59

Assisted Solution

by:Darius Ghassem
Darius Ghassem earned 200 total points
ID: 37806870
Take a look over this article by TigerMatt about time within AD http://tigermatt.wordpress.com/2009/08/01/windows-time-for-active-directory/

Second if you aren't syncing with a external time source then you could be seeing a time issue from BIOS time clock.

On client and member servers run this command this will make sure the server and clients are sync with DC that holds PDC emulator role.

http://technet.microsoft.com/en-us/library/cc758905(v=ws.10).aspx
0
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 

Author Comment

by:Rob Rudloff
ID: 37806971
Yes, SV1 is a domain controller.
I will read through those links you've posted.

In the Event Viewer, there was nothing in the way of an "error" or "information" or anything that looked bad regarding time syncing.  The only indication of anything "time-related" was with W32Time on SV2, but that was a month ago was realted to a network outage here.  SV1, as expected, showed no events regarding time syncing.

thanks.
0
 

Author Comment

by:Rob Rudloff
ID: 37806994
Important to note --

SV2 is the only machine on our network that is Server 2003, and it is the only machine that seems to have this problem.  All workstations (XP, W7) sync to SV1 and do not have this issue.
0
 

Author Comment

by:Rob Rudloff
ID: 37807037
Also, I am told by our network guy here that SV2 is actually syncing it's time with SV1 every 5 minutes (in an effort to fix this problem).  It's been set like that for a week, yet the problem occured this morning again -- AND -- the problem persisted through many 5-minute cycles.

We are assuming that the syncing happened many times, yet stayed exactly 60 seconds off-sync with the domain controller SV1.
0
 

Author Comment

by:Rob Rudloff
ID: 37807255
Update:  
Turns out, we have not one but two servers that are running Windows Server 2003 (SV2 and SV3).  Both of their clocks are off by 60 seconds.  Both sync their clocks with the domain controller SV1 (Server 2008R2).  SV2 is an exchange server, SV3 is a file server.  

All our other serves are Windows 2008 R2, and all of them are synced perfectly.
0
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 37807290
Did you run the command within the link I posted
0
 

Author Comment

by:Rob Rudloff
ID: 37812005
From the Event Viewer, we can tell that the "bad" server is trying to sync with the proper domain controller SV1, so that's good.

So, we ran:

    w32tm /config /syncfromflags:domhier /update
    net stop w32time
    net start w32time

A clue may be that then we run:
    w32tm /resync /rediscover
it does not do anything -- the clock remains un-synced. So, we fiddled with a registry settings for w32time and got that command to work.  However, that is something that we have to manually execute.

The big question is "why i it happening?"  -- One (or many) of our servers get exactly 60 off-sync with the domain controller SV1 ---  Why would that happen?
0
 

Author Comment

by:Rob Rudloff
ID: 37812074
A key point here is that the 60-second offset happens only on servers running Server 2003.  The domain controller is Server 2008.
0
 
LVL 4

Expert Comment

by:Red_Tech
ID: 37812158
Are you running in any virtual environment by chance?
0
 

Author Comment

by:Rob Rudloff
ID: 37812890
No, no virtual environments.  Everything here is pretty standard stuff.

Today we've been looking at event logs, etc.  We have not been able to figure out any sort of pattern as to "when" the servers get 60 seconds off-sync.  All workstations stay in sync, so we are still focusing on the Windows 2003 Servers.

One of the 2003 Servers is a VPN machine, and serves no other function.  (on top of that, it's never really VPN'd into).  The other 2003 Server is running IIS7 to run an intranet app we have here.
Both servers those were out-of-sync by 60 seconds when we checked them, but we can not tell if they became out-of-sync simultanously.
0
 
LVL 59

Assisted Solution

by:Darius Ghassem
Darius Ghassem earned 200 total points
ID: 37813389
w32tm /monitor
0
 

Author Comment

by:Rob Rudloff
ID: 37878872
hi.  Yes, we were using the "w32tm /monitor" command.  Since this is happening on production servers, we had to "drop back and punt" as they say -- we are now syncing the time on the Win2003 servers with the Win2008 domain server every 5 minutes, in an effort to keep everything in syns.  Why it's happening only on the Win2003 servers is a mystery.
0
 

Accepted Solution

by:
Rob Rudloff earned 0 total points
ID: 38243611
We are now trying to verify this with a MS Parnter as a bug in Win2003.  
However, we may be off of that OS shortly, so the problem may be avoided that way ...
0
 

Author Closing Comment

by:Rob Rudloff
ID: 38427981
We have given up -- it seems to be a bug in 2003, although there must be something unique here, since i assume everyone is suffering from this same problem.  We are moving to 2008 or 2012 soon, so maybe this will go away.
0

Featured Post

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I was supporting a handful of Windows 2008 (non-R2) 2 node clusters with shared quorum disks. Some had SQL 2008 installed and some were just a vendor application that we supported. For the purposes of this article it doesn’t really matter which so w…
New Windows 7 Installations take days for Windows-Updates to show up and install. This can easily be fixed. I have finally decided to write an article because this seems to get asked several times a day lately. This Article and the Links apply to…
This tutorial will walk an individual through the steps necessary to configure their installation of BackupExec 2012 to use network shared disk space. Verify that the path to the shared storage is valid and that data can be written to that location:…
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…

860 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question