ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Time Slip - Same LAN - Secondary DC

    IT Discussion
    5
    8
    946
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • DustinB3403D
      DustinB3403
      last edited by

      So our secondary DC slipped by over 10 minutes, I found it and reset the time with

      net time /set /yes
      

      But I'm curious as to why this would have slipped so much, so quickly. I'm not seeing any of our other systems as having slipped in the least.

      dafyreD 1 Reply Last reply Reply Quote 0
      • dafyreD
        dafyre @DustinB3403
        last edited by

        @DustinB3403 said:

        So our secondary DC slipped by over 10 minutes, I found it and reset the time with

        net time /set /yes
        

        But I'm curious as to why this would have slipped so much, so quickly. I'm not seeing any of our other systems as having slipped in the least.

        What is the secondary system set to use for its time server?

        DustinB3403D 1 Reply Last reply Reply Quote 0
        • DustinB3403D
          DustinB3403 @dafyre
          last edited by

          @dafyre Our PDC is the time source.

          So maybe the internal clock on this system is shot?

          dafyreD 1 Reply Last reply Reply Quote 0
          • dafyreD
            dafyre @DustinB3403
            last edited by

            @DustinB3403 said:

            @dafyre Our PDC is the time source.

            So maybe the internal clock on this system is shot?

            I know that used to happen if the CMOS battery was dying, but it usually involved a power outage too.

            DashrenderD J 2 Replies Last reply Reply Quote 2
            • DashrenderD
              Dashrender @dafyre
              last edited by

              @dafyre said:

              @DustinB3403 said:

              @dafyre Our PDC is the time source.

              So maybe the internal clock on this system is shot?

              I know that used to happen if the CMOS battery was dying, but it usually involved a power outage too.

              Exactly - did the secondary loose network connectivity or reboot? Should rarely care what the BIOS says after it's up and running. I don't know what the default let's check the PDC to make sure our clock is right setting is?

              1 Reply Last reply Reply Quote 0
              • Mike DavisM
                Mike Davis
                last edited by Mike Davis

                I had this happen on a Windows VM where the ESXi host time server was set to nist.time.gov The DNS server was set to a DNS server that I decommissioned about a month after I built the ESXi host... One day the VM restarted, grabbed the time from the host and was off by a bit.

                I said that to say we'll need a little more information to be able to figure out why yours drifted...

                DustinB3403D 1 Reply Last reply Reply Quote 0
                • J
                  Jason Banned @dafyre
                  last edited by Jason

                  @dafyre said:

                  @DustinB3403 said:

                  @dafyre Our PDC is the time source.

                  So maybe the internal clock on this system is shot?

                  I know that used to happen if the CMOS battery was dying, but it usually involved a power outage too.

                  Why are you using its internal clock. Set it to a public ntp source as reliable and have it pull from there. You should rarely use the bios clock, and never use it if it's a VM.

                  http://jackstromberg.com/2013/10/configuring-external-time-source-on-your-primary-domain-controller/

                  1 Reply Last reply Reply Quote 0
                  • DustinB3403D
                    DustinB3403 @Mike Davis
                    last edited by

                    @Mike-Davis Both of our DC's are physical at the moment.

                    Our primary DC reaches out to a public time source, and everything else is supposed to sync with that DC.

                    1 Reply Last reply Reply Quote 0
                    • 1 / 1
                    • First post
                      Last post