Synchronizing time with external source on 2088 r2
My domain controller isn't synchronized to a valid time source.   In an attempt to follow some instructions I get the following error

C:\>w32tm /config /syncfromflags:manual /manualpeerlist: "0.ntp.pool.org, 1.ntp.pool.org, 2.ntp.pool.org"

The following arguments were unexpected:
 0.ntp.pool.org, 1.ntp.pool.org, 2.ntp.pool.org


C:\>

_Instructions I was following___________
  1. First, locate your PDC
  2.  Server. Open the command prompt and type: C:\>netdom /query fsmo
  3. Log in to your PDC Server and open the command prompt.
  4. Stop the W32Time service: C:\>net stop w32time
  5. Configure the external time sources, type: C:\> w32tm /config /syncfromflags:manual /manualpeerlist: “0.ntp.pool.org, 1.ntp.pool.org, 2.ntp.pool.org”
  6. Make your PDC a reliable time source for the clients. Type: C:\>w32tm /config /reliable:yes
  7. Start the w32time service: C:\>net start w32time
  8. The windows time service should begin synchronizing the time. You can check the external NTP servers in the time configuration by typing: C:\>w32tm /query /configuration
  9. Check the Event Viewer for any errors.

thx

January 20th, 2010 8:03pm

Hi CPMTECH,

To configure the Windows Time Service on first forest root domain controller

  1. Log on to the domain controller.
  2. Type the following command to display the time difference between the local computer and a target computer, and then press ENTER:

    w32tm /stripchart /computer:target/samples:1/dataonly

    Where target specifies the DNS name or IP address of the NTP server that you are comparing the local computer's time against, such as time.windows.com and 1 specifies the number of time samples that will be returned from the target computer. In this example, only one sample will be returned to test basic NTP communication.
  3. Open UDP port 123 for outgoing traffic if needed.
  4. Open UDP port 123 (or a different port you have selected) for incoming NTP traffic.

    Type the following command to configure the PDC emulator and then press ENTER:

    w32tm /config /manualpeerlist:peers /syncfromflags:manual /reliable:yes /update

    Peers specifies the list of DNS names and/or IP addresses of the NTP time source that the PDC emulator synchronizes from. For example, you can specify time.windows.com. When specifying multiple peers, use a space as the delimiter and enclose them in quotation marks.

    http://technet.microsoft.com/en-us/library/cc784929(WS.10).aspx

Skip step 2 complete step 5 first then step 2.

Checkout if thi

Free Windows Admin Tool Kit Click here and download it now
January 20th, 2010 9:48pm

The peer list entries are space delimited. 

Try this:

w32tm /config /syncfromflags:manual /manualpeerlist: "0.ntp.pool.org,0x1 1.ntp.pool.org,0x1 2.ntp.pool.org,0x1"

Tony
January 20th, 2010 9:53pm

Hi CPMTECH,

Below are two which I have test on my (test DC) Windows Server 2008 R2 which working correctly. 

w32tm /config /manualpeerlist:"0.asia.pool.ntp.org 1.asia.pool.ntp.org 2.asia.pool.ntp.org" /syncfromflags:manual /reliable:yes /update

w32tm /config /manualpeerlist:"0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org" /syncfromflags:manual /reliable:yes /update

http://www.pool.ntp.org/en/use.htm


Try to get it right, so try again. 

Take Note : there are some typing error in your time server name

Free Windows Admin Tool Kit Click here and download it now
January 21st, 2010 4:06pm

Hello -

Can you tell me what the Hex parameter is after the ntpserver?

I tried looking in the w32tm help page but the parameter is not described.

Its seems to be a sync timing paramter 0x9 = 3600 seconds

Mine is/was X.Y.X.IP1,0x9 because that is what MS has when it points to mstime.com by default.

I added a second server with:

....../manualpeerlist:"X.Y.Z.IP1,0x9 X.Y.Z.IP2,0x9"  (notice the space)


  • Edited by rs120p Thursday, March 29, 2012 7:02 PM clarify
March 29th, 2012 6:15pm

Hi rs120p

http://blogs.msdn.com/b/w32time/archive/2008/02/26/configuring-the-time-service-ntpserver-and-specialpollinterval.aspx

The above blogs might answer your question.

Also 0x9 is not the correct flags.

Free Windows Admin Tool Kit Click here and download it now
April 16th, 2012 4:09pm

Hi Justohelp,

The article has 2 people ask for clarity if 0x9 = 0x1 plus 0x8 and was never answered.

Use scientific in your Windows calc program.

Also at the end it says the default for Server 2008 - which I have - is: 0x9.

And finally - the absolute do nothing default in Server 2008 registry says:

time.windows.com,0x9

Thank you for the link to the meaning of the flags

April 16th, 2012 4:28pm

I see the problem in your syntax but it looks like nobody has noticed it yet.

From my own tests:

w32tm /config /syncfromflags:manual /manualpeerlist: "0.ntp.pool.org,0x1 1.ntp.pool.org,0x1 2.ntp.pool.org,0x1"
The following arguments were unexpected:
 0.ntp.pool.org,0x1 1.ntp.pool.org,0x1 2.ntp.pool.org,0x1

w32tm /config /syncfromflags:manual /manualpeerlist:"0.ntp.pool.org,0x1 1.ntp.pool.org,0x1 2.ntp.pool.org,0x1"
The command completed successfully.

So where is the magic difference?

--> There should not be a space between the : and the first "

Free Windows Admin Tool Kit Click here and download it now
January 8th, 2015 10:03am

In addition to the erroneous comma-delimited server names and space after "manualpeerlist:", the time server FQDN's are incorrect. These 3 commands worked for me (the first line is wrapped):

w32tm /config /syncfromflags:manual /manualpeerlist:"0.pool.ntp.org,0x1 1.pool.ntp.org,0x1 2.pool.ntp.org,0x1"

net stop w32time

net start w32time

You should see some Event ID 37 entries in your System Event Log, something to this extent:

The time provider NtpClient is currently receiving valid time data from 0.pool.ntp.org,0x1 (ntp.m|0x1|0.0.0.0:123->38.104.197.228:123).

The time provider NtpClient is currently receiving valid time data from 1.pool.ntp.org,0x1 (ntp.m|0x1|0.0.0.0:123->132.163.4.101:123).

February 23rd, 2015 8:55pm

I kept getting the "The following arguments were unexpected:" error and none of the recommendations given in the replies on this page worked. I tried using space to separate, I tried adding ",0x1" to each element, I made sure I had no space after the colon, and so on. Nothing worked !

Then I tried the exact same command from a PS prompt rather than a CMD prompt. Voila!

That worked!

So try a PS prompt instead.

(this was on Windows Server 2012)

Free Windows Admin Tool Kit Click here and download it now
July 31st, 2015 2:44pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics