SharePoint server time issue.
Question
-
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.
- Edited by ghsajith Tuesday, July 21, 2020 8:31 AM update
Answers
-
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.- Proposed as answer by Jerry Xu4869Microsoft contingent staff Thursday, July 23, 2020 1:09 AM
- Marked as answer by ghsajith Friday, July 24, 2020 10:42 AM
- Edited by Qinghui MengMicrosoft contingent staff Monday, August 1, 2022 9:30 AM update for accessibility
All replies
-
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.- Proposed as answer by Jerry Xu4869Microsoft contingent staff Wednesday, July 22, 2020 2:31 AM
- Edited by Qinghui MengMicrosoft contingent staff Monday, August 1, 2022 9:31 AM update for accessibility
-
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.- Proposed as answer by Jerry Xu4869Microsoft contingent staff Thursday, July 23, 2020 1:09 AM
- Marked as answer by ghsajith Friday, July 24, 2020 10:42 AM
- Edited by Qinghui MengMicrosoft contingent staff Monday, August 1, 2022 9:30 AM update for accessibility
