Re: Server time on DC time lags 1:30 sec from NTP source?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



"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've 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






I've never checked exact differences between a time source and time 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-Windows-Time-Service.html
http://windowsitpro.com/article/articleid/8383/windows-time-synchronization-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-windows-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.


.



Relevant Pages

  • Re: Server time on DC time lags 1:30 sec from NTP source?
    ... Maybe you cna use another time source to get closer, personal i never realized this differences with our time. ... time server Server 2003 uses should be time-windows.com and not ... Time sync by client to DC ... packets, the client adjusts its local time based on the target (i.e., ...
    (microsoft.public.windows.server.active_directory)
  • Re: Clock and Network Simulator
    ... Forget everything except the tools that come with the NTP distribution. ... stable server and light up a selected client. ... If you increase the poll interval by one, the impulse response will look the same, but at double the time scale. ... Assume the server and all downstream clients are started at the same time. ...
    (comp.protocols.time.ntp)
  • Re: NTP orphan mode with manycast configuration
    ... multicast/broadcast and manycast are entirely different modes. ... the client listens on the ... NTP packet every 64 seconds. ... When the client first hears a server a ...
    (comp.protocols.time.ntp)
  • Re: avoiding large steps (on time island)
    ... I have a number of ntp clients connecting to one ntp server using ... its local clock driver. ... Once solution is to make the client boot process block until the client ...
    (comp.protocols.time.ntp)
  • Re: 1 Machine, 2 NICs, 2 Instances of ntpd; Possible?
    ... This _is_ what I'd call the 'client part'. ... Currently NTP uses port 123/UDP for both the source and destination ... polling a server that enforces the NTP port. ... processes which both require high priority access to the system clock. ...
    (comp.protocols.time.ntp)