increase in time between domain server and controllers
Dear All,
what will happen if time between domain server and controllers increase in an internal time synchronization configuration?
what will happen if time between domain server and controllers increase in an internal time synchronization configuration?
Answers
Most (all?) ABB PLCs, eg AC 800M does not care about any time offset with the domain, but Microsoft Kerberos authentication protocol may fail if time is skewed more than five minutes between the DC and the domain member computer who wants to perform authentication.
https://docs.microsoft.com/en-us/windows/security/threat-protection/security-po
licy-settings/maximum-tolerance-for-computer-clock-synchronization
https://docs.microsoft.com/en-us/windows/security/threat-protection/security-po
licy-settings/maximum-tolerance-for-computer-clock-synchronization
The PLC's wont care. The control application software will continue to run.
But a number of other very serious problems can start to happen. As Stephan says, the windows authentication service will begin to fail. This in turn causes other services to fail because they cannot log in. In extreme cases, OPC-DA and History access between node will fail, rebooting the operator stations will kick them off the domain network and you could be unable to log in to any clients or servers.
Don't let this happen. Fix the time synch settings and make sure all the controllers, clients and servers are at the correct time.
But a number of other very serious problems can start to happen. As Stephan says, the windows authentication service will begin to fail. This in turn causes other services to fail because they cannot log in. In extreme cases, OPC-DA and History access between node will fail, rebooting the operator stations will kick them off the domain network and you could be unable to log in to any clients or servers.
Don't let this happen. Fix the time synch settings and make sure all the controllers, clients and servers are at the correct time.
Add new comment