locked
SharePoint server time issue. RRS feed

  • Pertanyaan

  • WCF Client from office used to connect WCF Service implemented in SharePoint 2013 Portal hosted in DMZ.

    The SharePoint  Server time always lags behind the actual time. If we fix the time also, after a month or two, the time changes.  Because of that we are getting the following error while running the wcf client from the client machine. If we fix the sharepoint server time, it works fine.

    An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.
     


    • Diedit oleh ghsajith Selasa, 21 Juli 2020 08.31 update
    Selasa, 21 Juli 2020 08.30

Jawaban

  • Yes, most authentication and authorization protocols rely on minimal clock skew between the client and server. By default, this means a clock skew in Active Directory (for all clients/servers) of <5 minutes, but in reality your clients/servers shouldn't have a clock skew of 1 - 2 or more seconds. See https://support.microsoft.com/en-us/help/816042/how-to-configure-an-authoritative-time-server-in-windows-server for more info.

    Trevor Seward

    Office Apps and Services MVP



    Author, Deploying SharePoint 2019

    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Rabu, 22 Juli 2020 23.41

Semua Balasan

  • Hi

    How does the time change? Change to another timezone or back to zero?


    Justin Liu Office Apps & Services MVP, MCSE
    Senior Software Engineer
    Learn Microsoft 365 from Microsoft DOCs now!
    Please Vote and Mark as Answer if it helps you.

    Rabu, 22 Juli 2020 00.54
  • If you're running it as a VM, look at time synchronization with the VM host. This should be disabled.

    Trevor Seward

    Office Apps and Services MVP



    Author, Deploying SharePoint 2019

    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Rabu, 22 Juli 2020 00.58
  • 5 mintes slow than the actual time.
    Rabu, 22 Juli 2020 04.51
  • Is it important to keep the same time between client and server ?
    Rabu, 22 Juli 2020 04.52
  • Yes, most authentication and authorization protocols rely on minimal clock skew between the client and server. By default, this means a clock skew in Active Directory (for all clients/servers) of <5 minutes, but in reality your clients/servers shouldn't have a clock skew of 1 - 2 or more seconds. See https://support.microsoft.com/en-us/help/816042/how-to-configure-an-authoritative-time-server-in-windows-server for more info.

    Trevor Seward

    Office Apps and Services MVP



    Author, Deploying SharePoint 2019

    Author, Deploying SharePoint 2016

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Rabu, 22 Juli 2020 23.41
  • Hi,

     

    Thanks for your response.

     

    All English SharePoint forums will be migrating to a new home on Microsoft Q&A . If you have any questions about SharePoint, welcome to post it on the new home.

     

    Best Regards

    Jerry


    "SharePoint" forums will be migrating to a new home on Microsoft Q&A !
    We invite you to post new questions in the "SharePoint" forums' new home on Microsoft Q&A !

    Senin, 03 Agustus 2020 07.26