locked
Account Locked RRS feed

  • Question

  • Testing scenarios requires going forward and backward in date without changing the DC date.

    on trying to logon to the testing server with the date difference, accounts locks.

    we were able to access those testing servers from windows 2003 servers but not from newer versions.

    is there any way to achieve the same from windows 10 clients?

    we need to access for example a server with date July-2018 from windows 10 client without getting the account locked, is this possible?

    Sunday, April 3, 2016 1:28 PM

Answers

  • Hello,

    By default Kerberos will not let you login when the time difference between peers is more than 5 minutes. However you can play with this value. The setting that you may want to change is Maximum tolerance for computer clock synchronizationhttps://technet.microsoft.com/en-us/library/cc779260(v=ws.10).aspx

    Regards

    • Proposed as answer by Alvwan Monday, April 4, 2016 2:29 AM
    • Marked as answer by Waleed Amin Monday, April 4, 2016 1:39 PM
    Sunday, April 3, 2016 7:00 PM
  • Hi,

    I agree with Avendil, you should consider the maximum tolerance for computer clock synchronization and the possible values for this Group Policy setting are:

    • A user-defined number of minutes from 1 through 99,999

    • Not defined

    You should try to configure it as not defined to have a test.

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by Waleed Amin Monday, April 4, 2016 1:39 PM
    Monday, April 4, 2016 2:29 AM

All replies

  • Hello,

    By default Kerberos will not let you login when the time difference between peers is more than 5 minutes. However you can play with this value. The setting that you may want to change is Maximum tolerance for computer clock synchronizationhttps://technet.microsoft.com/en-us/library/cc779260(v=ws.10).aspx

    Regards

    • Proposed as answer by Alvwan Monday, April 4, 2016 2:29 AM
    • Marked as answer by Waleed Amin Monday, April 4, 2016 1:39 PM
    Sunday, April 3, 2016 7:00 PM
  • Hi,

    I agree with Avendil, you should consider the maximum tolerance for computer clock synchronization and the possible values for this Group Policy setting are:

    • A user-defined number of minutes from 1 through 99,999

    • Not defined

    You should try to configure it as not defined to have a test.

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by Waleed Amin Monday, April 4, 2016 1:39 PM
    Monday, April 4, 2016 2:29 AM
  • thanks a lot for your reply, that is exactly what we are searching for.

    is there any way to get value more than the 99999 max value? as testing can reach a year forward or backward.

    Monday, April 4, 2016 1:41 PM
  • Hi,

    As far as I know, there is no such a way to exceed the default value range.

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, April 5, 2016 2:04 AM
  • Thanks a lot
    Wednesday, April 6, 2016 7:37 AM