+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 18
Windows Server 2008 R2 Thread, Confusion ovet time sync ! in Technical; ...
  1. #1
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,301
    Thank Post
    80
    Thanked 46 Times in 32 Posts
    Rep Power
    31

    Confusion ovet time sync !

    My PDC had system event log errors:


    Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.

    I've now run the following:

    C:\>net stop w32time

    Configure external time sources, type: C:\> w32tm /config /syncfromflags:manual /manualpeerlist:”0.uk.pool.ntp.org,1.uk.pool.ntp.or g,2.uk.pool.ntp.org,3.uk.pool.ntp.org”

    Made PDC a reliable time source for the clients. Type: C:\>w32tm /config /reliable:yes

    Start the w32time service: C:\>net start w32time

    If I do C:\> w32tm /query /source on my other two Domain controllers they report back correctly with the PDC name.

    Clients when using the same query report back any of the DC's.

    I am unsure how the DC's and the windows 7 clients are getting this information, it seems not be via DHCP or Group Policy....

    Any ideas

  2. #2

    Join Date
    Sep 2013
    Posts
    8
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    It's by virtue of their domain membership.

  3. #3
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,301
    Thank Post
    80
    Thanked 46 Times in 32 Posts
    Rep Power
    31
    Both the other DC's NOT the PDC shows this error in the system event log weekly:

    Log Name: System
    Source: Microsoft-Windows-Time-Service
    Date: 17/01/2014 21:23:55
    Event ID: 142
    Task Category: None
    Level: Warning

    The time service has stopped advertising as a time source because the local clock is not synchronized.


    Which is what I am trying to solve....
    Last edited by kennysarmy; 23rd January 2014 at 03:33 PM.

  4. #4

    Michael's Avatar
    Join Date
    Dec 2005
    Location
    Birmingham
    Posts
    9,262
    Thank Post
    242
    Thanked 1,572 Times in 1,252 Posts
    Rep Power
    340
    I believe by default the 2008 R2 PDC automatically acts as the time server, which is why it's important to configure your server with a real NTP server, be it external or the Local Authority.

  5. #5
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,301
    Thank Post
    80
    Thanked 46 Times in 32 Posts
    Rep Power
    31
    Quote Originally Posted by Michael View Post
    I believe by default the 2008 R2 PDC automatically acts as the time server, which is why it's important to configure your server with a real NTP server, be it external or the Local Authority.
    I think I've done that bit now....

    It's just not knowing if this will sort the errors on the other DC;s (see post above)

    The times on all three DC's seem to be in sync I might add....

  6. #6

    Join Date
    Sep 2010
    Posts
    583
    Thank Post
    26
    Thanked 66 Times in 61 Posts
    Rep Power
    21
    +1 on the above
    all DC's look to the Operations Master for time syncing

    i believe there is an option in W32time to query the time source to see if you get a response might be worth trying that

  7. #7
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,301
    Thank Post
    80
    Thanked 46 Times in 32 Posts
    Rep Power
    31
    w32tm /query /configuration on the DC's which are not the PDC return:

    C:\Windows\system32>w32tm /query /configuration
    [Configuration]

    EventLogFlags: 2 (Local)
    AnnounceFlags: 10 (Local)
    TimeJumpAuditOffset: 28800 (Local)
    MinPollInterval: 6 (Local)
    MaxPollInterval: 10 (Local)
    MaxNegPhaseCorrection: 172800 (Local)
    MaxPosPhaseCorrection: 172800 (Local)
    MaxAllowedPhaseOffset: 300 (Local)

    FrequencyCorrectRate: 4 (Local)
    PollAdjustFactor: 5 (Local)
    LargePhaseOffset: 50000000 (Local)
    SpikeWatchPeriod: 900 (Local)
    LocalClockDispersion: 10 (Local)
    HoldPeriod: 5 (Local)
    PhaseCorrectRate: 7 (Local)
    UpdateInterval: 100 (Local)


    [TimeProviders]

    NtpClient (Local)
    DllName: C:\Windows\system32\w32time.dll (Local)
    Enabled: 1 (Local)
    InputProvider: 1 (Local)
    CrossSiteSyncFlags: 2 (Local)
    AllowNonstandardModeCombinations: 1 (Local)
    ResolvePeerBackoffMinutes: 15 (Local)
    ResolvePeerBackoffMaxTimes: 7 (Local)
    CompatibilityFlags: 2147483648 (Local)
    EventLogFlags: 1 (Local)
    LargeSampleSkew: 3 (Local)
    SpecialPollInterval: 3600 (Local)
    Type: NT5DS (Local)

    NtpServer (Local)
    DllName: C:\Windows\system32\w32time.dll (Local)
    Enabled: 1 (Local)
    InputProvider: 0 (Local)
    AllowNonstandardModeCombinations: 1 (Local)

    VMICTimeProvider (Local)
    DllName: C:\Windows\System32\vmictimeprovider.dll (Local)
    Enabled: 1 (Local)
    InputProvider: 1 (Local)

  8. #8

    Join Date
    Sep 2013
    Posts
    8
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Assuming your machines aren't VMs then MS advice is as follows:
    On all other DCs use:

    net stop w32Time w32tm /unregister w32tm /register net start w32time to reset the time service to use NT5DS (value of which is stored here; HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\W32Time\Parameters )

    VM DCs should all point to the same external time provider as they pass time depending on CPU usage and often end up out of sync.

  9. #9
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,301
    Thank Post
    80
    Thanked 46 Times in 32 Posts
    Rep Power
    31
    On the PDC:

    C:\Windows\system32>w32tm /resync
    Sending resync command to local computer
    The computer did not resync because no time data was available.

  10. #10
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,301
    Thank Post
    80
    Thanked 46 Times in 32 Posts
    Rep Power
    31
    Quote Originally Posted by hummingtech View Post
    Assuming your machines aren't VMs then MS advice is as follows:
    On all other DCs use:

    net stop w32Time w32tm /unregister w32tm /register net start w32time to reset the time service to use NT5DS (value of which is stored here; HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\W32Time\Parameters )

    VM DCs should all point to the same external time provider as they pass time depending on CPU usage and often end up out of sync.
    Hi.

    The PDC is physical and other two domain controllers are VM's.....

  11. #11

    Join Date
    Sep 2013
    Posts
    8
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Do you have firewalls on?

  12. #12
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,301
    Thank Post
    80
    Thanked 46 Times in 32 Posts
    Rep Power
    31
    PDC does nt look right

    C:\Windows\system32>w32tm /query /source
    Local CMOS Clock

    C:\Windows\system32>w32tm /query /peers
    #Peers: 1

    Peer: "0.uk.pool.ntp.org,1.uk.pool.ntp,2.uk.pool.ntp.org ,3.uk.pool.ntp.org"
    State: Pending
    Time Remaining: 847.0535070s
    Mode: 0 (reserved)
    Stratum: 0 (unspecified)
    PeerPoll Interval: 0 (unspecified)
    HostPoll Interval: 0 (unspecified)

    C:\Windows\system32>

  13. #13
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,301
    Thank Post
    80
    Thanked 46 Times in 32 Posts
    Rep Power
    31
    Quote Originally Posted by hummingtech View Post
    Do you have firewalls on?
    Firewall is turned off....

  14. #14

    Join Date
    Sep 2013
    Posts
    8
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Did you stop and start the time service after updating, and have you set the syncfromflags bit to facilitate autoupdating?

  15. #15
    kennysarmy's Avatar
    Join Date
    Oct 2005
    Location
    UK
    Posts
    1,301
    Thank Post
    80
    Thanked 46 Times in 32 Posts
    Rep Power
    31
    C:\Windows\system32>tracert 0.uk.pool.ntp.org

    Tracing route to 0.uk.pool.ntp.org [176.58.109.199]
    over a maximum of 30 hops:

    1 1 ms 1 ms 1 ms 10.107.93.254
    2 <1 ms <1 ms <1 ms 10.107.95.253
    3 7 ms 7 ms 7 ms 10.104.58.223
    4 9 ms 9 ms 7 ms 192.168.65.254
    5 7 ms 6 ms 6 ms 192.168.168.61
    6 7 ms 7 ms 7 ms 46.60.252.190
    7 6 ms 6 ms * globix-gw-a.lonap.net [5.57.80.95]
    8 7 ms 7 ms 7 ms 85.90.238.69
    9 8 ms 8 ms 8 ms 212.111.33.238
    10 7 ms 8 ms 7 ms time.videxio.net [176.58.109.199]

    Trace complete.

SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. Hyper V host - Time Sync
    By LukeC in forum Windows Server 2008 R2
    Replies: 4
    Last Post: 4th December 2012, 09:19 AM
  2. Sync Time With DC
    By FN-GM in forum Windows Server 2008 R2
    Replies: 9
    Last Post: 9th August 2011, 10:16 AM
  3. user not syncing with time server
    By techie211 in forum Windows Server 2000/2003
    Replies: 5
    Last Post: 19th March 2009, 07:28 PM
  4. Remote PC shutdown tools - AD and Time sync
    By sycho666 in forum Windows
    Replies: 1
    Last Post: 20th April 2007, 08:25 AM
  5. Best way / method to sync time between servers.
    By mac_shinobi in forum Wireless Networks
    Replies: 10
    Last Post: 27th September 2005, 01:40 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •