Re: Server time on DC time lags 1:30 sec from NTP source?
- From: Douggg <Douggg@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 10 Oct 2009 08:26:02 -0700
Not sure how I could get a closer time source. The RTT is 70 msec to the NTP
server. I just can't figure out why MSFT lags 1:30 seconds.
"Meinolf Weber [MVP-DS]" wrote:
Hello Douggg,.
Maybe you cna use another time source to get closer, personal i never realized
this differences with our time.
See here for some other time sources:
http://www.pool.ntp.org/
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
I've read through your reply and the blog posts. The take away
message I'm getting here is that MSFT's keeps sloppy time which is by
design. The posts make it sound like anything 5 minutes or less off
from actual time is acceptable by MSFT's standards. (Did I get that
right?)
I'm also finding it very hard to beleive that a server connected to a
T1 to the Interet would drift (behind) 1:30 secounds. But in reading
the posts, it appears that's within Microsoft's specs.
Did I get that right?
Is there any way to get any closer? Like say 10 seconds?
"Ace Fekay [MCT]" wrote:
"Douggg" <Douggg@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0114ACAD-C39F-4540-B249-52F8EBB0D91E@xxxxxxxxxxxxxxxx
I'm working with a non-profit who has AD on Server 2003. They'veI've never checked exact differences between a time source and time
been
putting up with a time problem, the DC that's the authorative time
source
for
the domain is off (slow) by 1:30 sec from the NTP source.
time.windows.com
Not sure how this can happen with NTP.
In researching this issue I found some documenttion saying the NTP
time server Server 2003 uses should be time-windows.com and not
time.windows.com.
Can someone confirm the NTP sever?
Any idea why the Server's time would lag 1:30 sec behind the NTP
server?
What utility can I use to Dx the problem?
Any assistance would be appreciated.
Thanks,
Douggg
on a server down to the second. Read the info below. I believe the 2
minute tolerance is what you are seeing, since the authoritive time
server on the domain (PDC Emulator), acts as a time client to its
external source.
==================================================================
Time sync by client to DC
How to configure an authoritative time server in Windows Server 2003
http://support.microsoft.com/kb/816042
Quoted from the above link:
All client desktop computers nominate the authenticating domain
controller
as their in-bound time partner.
All member servers follow the same process that client desktop
computers
follow.
All domain controllers in a domain nominate the primary domain
controller
(PDC) operations master as their in-bound time partner.
All PDC operations masters follow the hierarchy of domains in the
selection
of their in-bound time partner.
In this hierarchy, the PDC operations master at the root of the
forest
becomes authoritative for the organization
The following quote is on the time algorithm in Windows 2000, which I
haven't seen any evidence that it has changed:
http://www.windowsnetworking.com/articles_tutorials/Configuring-Windo
ws-Time-Service.html
http://windowsitpro.com/article/articleid/8383/windows-time-synchroni
zation-service.html
"When a client workstation (i.e., a Windows 2000 Professional-Win2K
Pro-machine) boots, it contacts a domain controller for
authentication. When the two computers exchange authentication
packets, the client adjusts its local time based on the target (i.e.,
the domain controller's) time. If the target time is ahead of local
(i.e., the client's) time by less than 2 minutes, the client
immediately adjusts its time to match the target time. If the target
time is behind the local time by less than 2 minutes, the client
slows its clock over a period of 20 minutes until the two times are
in synch. If the local time is off by more than 2 minutes, the client
immediately sets its time to match the target time. . . . "
---
Troubleshooting time service:
To debug the time service:
http://blogs.msdn.com/w32time/archive/2008/02/28/configuring-the-time
-service-enabling-the-debug-log.aspx
How to manually sync time between domain client and local time server
http://support.microsoft.com/kb/555225
==================================================================
More info from my blog, which I will be adding the above information
to.
Configuring the Windows Time Service for Windows Server
http://msmvps.com/blogs/acefekay/archive/2009/09/18/configuring-the-w
indows-time-service-for-windows-server.aspx
-- Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit
among responding engineers, and to help others benefit from your
resolution.
Ace Fekay, MCT, MCTS 2008, MCTS Exchange, MCSE, MCSA 2003 & 2000,
MCSA
Messaging
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone
numbers.
- References:
- Server time on DC time lags 1:30 sec from NTP source?
- From: Douggg
- Re: Server time on DC time lags 1:30 sec from NTP source?
- From: Ace Fekay [MCT]
- Re: Server time on DC time lags 1:30 sec from NTP source?
- From: Douggg
- Re: Server time on DC time lags 1:30 sec from NTP source?
- From: Meinolf Weber [MVP-DS]
- Server time on DC time lags 1:30 sec from NTP source?
- Prev by Date: Re: difference between Assign and Publish a software
- Next by Date: Re: Server time on DC time lags 1:30 sec from NTP source?
- Previous by thread: Re: Server time on DC time lags 1:30 sec from NTP source?
- Next by thread: Re: Server time on DC time lags 1:30 sec from NTP source?
- Index(es):
Relevant Pages
|
