none
Client time refer to old pdc RRS feed

  • Question

  • hi everyone

    i have a domain with 2 DCs (dc1 dc2). A Couple weeks ago  my dc1 failed and i had to seize fsmo roles to dc2. after that i config NTP Server on new fsmo server (dc2)and direct client to that by gpo.

    after i setup new dc to replace failed dc1, i accidentally seize (not transfer) fsmo from active dc2 to new dc1.

    after that config new dc1 as ntp server in domain and direct client to that by gpo again.

    now some client refer to dc2 as ntp server and some refer to dc1. how can i solve this?

    on dc2 :

    w32tm /config /syncfromflags:domhier /reliable:no /update

    net stop w32time

    net start w32time

    w32tm /config /syncfromflags:domhier /update

    some command output:

    netdom /query fsmo

    Schema master               DC1.xxx.net
    Domain naming master        DC1.xxx.net
    PDC                         DC1.xxx.net
    RID pool manager            DC1.xxx.net
    Infrastructure master       DC1.xxx.net

    -----------------------------------------------------------------------------------

    w32tm /monitor /domain:xxx.net
    DC2.xxx.net[192.168.0.4:123]:
        ICMP: 0ms delay
        NTP: +6.3859556s offset from DC1.xxx.net
            RefID: DC1.xxx.net [192.168.0.3]
            Stratum: 5
    DC1.xxx.net *** PDC ***[192.168.0.3:123]:
        ICMP: 0ms delay
        NTP: +0.0000000s offset from DC1.xxx.net
            RefID: ns3.time.com [1.1.1.1]
            Stratum: 4

    -------------------------------------------------------------------------------------------

    32tm /query /source
    DC2.xxx.net

    ----------------------------------------------------------------------------------------------

    W32tm /monitor

    CW32TM /query /status
    Leap Indicator: 0(no warning)
    Stratum: 6 (secondary reference - syncd by (S)NTP)
    Precision: -6 (15.625ms per tick)
    Root Delay: 0.2546159s
    Root Dispersion: 11.0767194s
    ReferenceId: 0xC0A80004 (source IP:  192.168.0.4)
    Last Successful Sync Time: 7/7/2019 11:42:15 AM
    Source: DC2.xxx.net
    Poll Interval: 10 (1024s)


    Sunday, July 7, 2019 7:18 AM

All replies

  • now some client refer to dc2 as ntp server

    Not clear what the issue is. All domain controllers (aside from PDCe) will get time from PDCe. All other member servers and desktops can get valid time from any domain controller.

    https://blogs.technet.microsoft.com/nepapfe/2013/03/01/its-simple-time-configuration-in-active-directory/

     

    (please don't forget to mark helpful replies as answer)

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.


    Sunday, July 7, 2019 12:19 PM
  • Hi,

    If i didn't misunderstand you ,here is your situation 

    Domain controller old dc 1 holding the PDC Emulator Role got crashed and you have seized the role to another domain controller dc2. and set a gpo for time client get time directly from dc2.

    Then, you have transferred PDC Emulator FSMO roles from dc2 domain controllers to new domain controller. set a gpo for time client get time from new dc .

    Is it related about the GPO (once for dc1, one for dc 2)?For a test ,just disable the gpo, will  it work?

    For configure the pdc, you can refer to  :

    https://social.technet.microsoft.com/wiki/contents/articles/8863.time-service-configuration-on-dc-with-pdc-emulator-fsmo-role.aspx

    Best Regards,

    Fan


    Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Tuesday, July 9, 2019 4:14 AM
  • Hi,

     

    Just want to confirm the current situations.

     

    Please feel free to let us know if you need further assistance.

     

    Best Regards,

    Fan


    Please remember to mark the replies as an answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

    Thursday, July 11, 2019 5:39 AM