locked
Can't get NTP time working on SErver 2008 R2 DC

    Question

  • I'm having a nightmare setting up the NTP time on our Server 2008 R2 Domain. All our servers are on Hyper-V, but for the PDC at least I have unticked the "Time synchronisation" Integration Services Management box, so I know the time is not coming from the source.

    On the PDC Emulator I ran this command:

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

    and

    net stop w32time && net start w32time

    This runs succesfully, but the time doesn't change (12 mins slow at the moment)

    When I run "w32tm /resync /rediscover"
    I get:
    -------------
    Sending resync command to local computer
    The computer did not resync because no time data was available.
    --------------

    and when I run w32tm /query /status
    I get:
    ------------------------
    Leap Indicator: 0(no warning)
    Stratum: 1 (primary reference - syncd by radio clock)
    Precision: -6 (15.625ms per tick)
    Root Delay: 0.0000000s
    Root Dispersion: 10.0000000s
    ReferenceId: 0x4C4F434C (source name:  "LOCL")
    Last Successful Sync Time: 26/01/2010 12:50:47
    Source: Local CMOS Clock
    Poll Interval: 10 (1024s)
    -------------------------

    So as you can see the Local CMOS is still the source.
    Can anyone help me? It's driving me nuts.

    Thanks
    Kieran
    Tuesday, January 26, 2010 1:30 PM

Answers

  • Hi Kieran,

    Please make sure you have followed all the suggestions below to setup the time server.

    How to configure an authoritative time server in Windows Server
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;816042

    Note: Virtual Machine will always sync with Hyper-V host at startup. This is required to boot strap the timer inside the virtual machine.

    If the issue persists, try the suggestions below:

    Time synchronization on my network
    http://social.technet.microsoft.com/Forums/en/winserverPN/thread/99f9d219-73d9-4d03-9fc4-f9c37a410c09

    Thanks.


    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by Kieran Walsh Friday, January 29, 2010 1:28 PM
    Wednesday, January 27, 2010 6:32 AM
    Moderator
  • Hi,

    Currently, I suggest correct the time on Hyper-V host (sync its time with time server) and restart the VM so that it could get correct indirectly.

    It seems your PDC cannot contact the external time server to get correct time. If so, it will query local CMOS clock instead. Please try to disable Firewall to test.

    If the issue persists, let’s try to monitor the network traffic when trying to sync time:

    Download Microsoft Network Monitor and install it on PDC.
    http://www.microsoft.com/downloads/details.aspx?FamilyID=983b941d-06cb-4658-b7f6-3088333d062f&displaylang=en  

    1. Run Network Monitor and start capturing. Run w32tm /resync /nowait
    2. Reproduce the problem.

    Stop the capturing, save the resultand use Windows Live SkyDrive (http://www.skydrive.live.com/) to upload the file. If you would like other community member to analyze the report, you can paste the link here, if not, you can send the link to tfwst@microsoft.com.
     
    Also, did you run " w32tm /query /status" on client systems? What’s the result?

    Thanks.


    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by Kieran Walsh Friday, January 29, 2010 1:28 PM
    Thursday, January 28, 2010 2:39 AM
    Moderator

All replies

  • Hi Kieran,

    Please make sure you have followed all the suggestions below to setup the time server.

    How to configure an authoritative time server in Windows Server
    http://support.microsoft.com/default.aspx?scid=kb;EN-US;816042

    Note: Virtual Machine will always sync with Hyper-V host at startup. This is required to boot strap the timer inside the virtual machine.

    If the issue persists, try the suggestions below:

    Time synchronization on my network
    http://social.technet.microsoft.com/Forums/en/winserverPN/thread/99f9d219-73d9-4d03-9fc4-f9c37a410c09

    Thanks.


    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by Kieran Walsh Friday, January 29, 2010 1:28 PM
    Wednesday, January 27, 2010 6:32 AM
    Moderator
  • Hi Mervyn,
    Thanks for the reply. My setup does follow that KB article, I wasn't sure if I needed to put ",0x1" after every peer, but doing that doesn't change anything - still looks to the local CMOS. (btw, is that something you can change in a Hyper-V machine, just doing that for now would help matters)

    As for the other thread, we don't have any captured snapshots either.

    Thanks
    Kieran
    Wednesday, January 27, 2010 10:23 AM
  • Hi,

    Currently, I suggest correct the time on Hyper-V host (sync its time with time server) and restart the VM so that it could get correct indirectly.

    It seems your PDC cannot contact the external time server to get correct time. If so, it will query local CMOS clock instead. Please try to disable Firewall to test.

    If the issue persists, let’s try to monitor the network traffic when trying to sync time:

    Download Microsoft Network Monitor and install it on PDC.
    http://www.microsoft.com/downloads/details.aspx?FamilyID=983b941d-06cb-4658-b7f6-3088333d062f&displaylang=en  

    1. Run Network Monitor and start capturing. Run w32tm /resync /nowait
    2. Reproduce the problem.

    Stop the capturing, save the resultand use Windows Live SkyDrive (http://www.skydrive.live.com/) to upload the file. If you would like other community member to analyze the report, you can paste the link here, if not, you can send the link to tfwst@microsoft.com.
     
    Also, did you run " w32tm /query /status" on client systems? What’s the result?

    Thanks.


    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by Kieran Walsh Friday, January 29, 2010 1:28 PM
    Thursday, January 28, 2010 2:39 AM
    Moderator
  • Yep, all working now - thanks for that. Turned out that I actually had to reboot the Host server too and then it all got sorted. Strange one.

    "Also, did you run " w32tm /query /status" on client systems? What’s the result?"

    I tried to do that but "/query" is not recognised on XP systems. Having the ability to do that check on the clients would be great though, is there another way to do it?

    Thanks
    Kieran
    Friday, January 29, 2010 1:27 PM
  • Hi Kieran,

    Glad to hear the suggestions worked. Regarding "query /status", as far as I know, there is no workaround. Sorry for the inconvenience. If you have more questions in the future, you’re welcomed to this forum.

    Thanks.


    This posting is provided "AS IS" with no warranties, and confers no rights.
    Monday, February 01, 2010 8:43 AM
    Moderator
  • That's OK, cheers for your help on this.

    Kieran

    Monday, February 01, 2010 10:11 AM