Time Provider NtpClient: An error occurred during DNS lookup of the manually configured peer ‘Server1,0x1’. NtpClient will try the DNS lookup again in 480 minutes. The error was: No such service is known. The service cannot be found in the specified name space. (0x8007277C)

We have this little Network, but for years now the time has been 20 minutes or so off.  Never had time to look at it till now.

So Googled for help on how to Setup “Microsoft Windows 2003 Time Server” and the first item on the list is :

How to configure an authoritative time server in Windows Server
http://support.microsoft.com/kb/816042#method2

So that is probably the most authoritative site \ source.

The Web docs two (not 99 ways to leave your lover or 99 Problems) routes to make the necessary correction:-

• Having Microsoft make the correction
• Or following the manual instructions (basically making a couple of MS Windows Registry Changes)

So that I can be a bit aware of the goings on, chose the manual steps.

Went down the line and mostly everything lined up.

But, somehow the Time Servers did not look quite good:

Branch:

HKEY_LOCAL_MACHINE
    \SYSTEM
       \CurrentControlSet
         \Services
            \w32time
              \Parameters

Name:

   NtpServer

Data:

   Server1,0x1

But, prior to making more changes, tried restarting the Time Service, but did not get too far.

To stop & restart, simple enter:

  net stop w32time
  net start w32time

So reviewed MS original web doc and went to the list of Time Servers:

A list of the Simple Network Time Protocol (SNTP) time servers that are available on the Internet:
http://support.microsoft.com/kb/262680

So now I know we have a “tiered” list of Servers.  As  understand it, there are some rules:

• stratum one time servers – http://support.ntp.org/bin/view/Servers/StratumOneTimeServers – But, it says not to use those as they are authoritative – Almost like DNS root domain servers
• stratum two time servers – http://support.ntp.org/bin/view/Servers/StratumTwoTimeServers – Advised that it is OK to use these ones, but check as only some would have “Open Access” for public use
• And, then there are the NTP Pool Servers – http://support.ntp.org/bin/view/Servers/NTPPoolServers

Basically, MS recommeds:

• Not to use “Stratum one time servers” as they “primarily intended to act as source time servers for second-level time servers”
• That it is OK to use “Stratum two time servers”, but to check and make sure that each one we will like to use is open for public use
• And for Workgroup computers MS Words are “Microsoft does recommend that workgroup computers sync from the Microsoft NTP server (time.windows.com).”

So basically, MS gives us all the Information we will ever need, but really a bit sanitized. Not much hand-holding.

So went off and Googled and found something quite useful.

Windows Time Service
http://support.ntp.org/bin/view/Support/WindowsTimeService

Windows domain controller machines that are part of an Active Directory domain are automatically configured to act as time servers. The first domain controller in the network is automatically configured to poll time.windows.com as a time source, and all subsequent domain controllors automatically obtain time from the first domain controller.

Windows domain member servers and domain member clients are automatically configured to receive time from domain controllers on the same network.

Stand-alone Windows servers and clients are automatically configured to poll time.windows.com at one-hour intervals. The time.windows.com server (actually a cluster of servers) is maintained by Microsoft. However, time.windows.com is notoriously unreliable and heavily loaded, so configuring a different time source or multiple sources is probably wise.

---

An example configuration, suitable for a Windows 2003 standalone server or the first domain controller in a Active Directory domain:

C:\>w32tm /config /update /manualpeerlist:"0.pool.ntp.org,0x8 1.pool.ntp.org,0x8 2.pool.ntp.org,0x8 3.pool.ntp.org,0x8" /syncfromflags:MANUAL

The above configuration tells Windows Time Service to use four servers from the NTP Pool, and use a client-mode association (identified by the ,0x8 after each server name) to contact them. This configuration is analgous to serverdirectives in the configuration file for ntpd. Note that this configuration should not be used on Windows servers or clients that are members of an Active Directory domain, unless you absolutely want them to ignore time from Active Directory domain controllers on the network.

So copied the entry above unto a file editor (notepad or hopefully notepad++) and ran it on the AD Server.

w32tm /config /update /manualpeerlist:"0.pool.ntp.org,0x8 1.pool.ntp.org,0x8 2.pool.ntp.org,0x8 3.pool.ntp.org,0x8" /syncfromflags:MANUAL

And, every looks good. The registry entries appear more work like:

Name : 
  NTP Server

Data :
  0.pool.ntp.org,0x8 1.pool.ntp.org,0x8 2.pool.ntp.org,0x8 
  3.pool.ntp.org,0x8

Tried syncing using:

   w32tm /resync

Quite a few years ago while in ATL Georgia I went for a walk. And, saw this stone that read the “Only Advantage of the Day”. I think it is a monument that dates back to the Civil War.

Will like to Google and see what it really means.

But, sometimes in LIFE the only Advantage of the day is a “Clear Help”.

So thank goodness to Microsoft and ntp.org for making so much free on the .Net