Problem on connectivity server time change and disconnect from the domain
Hello, can anyone help to to deal with these problems?
Current, I found 3 problems on my 800xA. I'm not sure they are all related to each other or not.
First, some historical trends were not response (data freeze) but the real-time value was active. And CS server (CS1 and CS2, CS1 is time service provider) time was changed to Y1970.
So, I have trial to disabling time sync in between CS server and Controller and disable time sync in 800xA application. The trends seemed back to work but response time when data value changing is delayed instead.
After that, try to enabled the time sync mode in 800xA back but the trends update is still delayed. After that, trying to force to sync the time in 800xA application by click ‘force-time sync’ in IM server then the trend response time seems back to normal. Currently, this condition is under monitoring but not sure it is the proper solution to the root cause of problem?
The second, according to CS server time changed as per problem#1, I also found the CS1 disconnected from domain. The result is live data in 800xA not response in OS workstations. I tried to re-join CS1 into the domain but CS1 still automatically disconnected from time to time. Finally, I try to set DNS server network to prefer AS2 instead AS1 in all servers and OS. CS1 seems back to normal but real-time trend on some computer OS workstation were not connect to CS1 server while some connect to both CS1/CS2 normally.
Can any suggest for further thing to do or to be check.
Thank you very much
The clock synchronization does not disrupts by itself - there must be something you have in your configuration that causes the so disruptive time jumps.
Domain controller time must be kept in sync with all domain member computers, +/- 5 minutes, or else the Kerberos Authentication Protocol of Microsoft Windows may start to break down. After 60 days the Secure Channel Password will expire and may cause domain controllers to stop synchronize. Not to mention the Active Directory Tombstone Lifetime (180 days, IIRC). The Microsoft DFSR Replication is also sensitive for time skew.
To put it short, a bad time is very very very bad news to a Microsoft Windows domain.
An always correct time is paramount to run a Microsoft Windows domain and System 800xA.
To be able to assist, I would need a complete description of the system, especially the time sync parts. What PLCs do you have? How are they synchronized? How are the domain controllers synchronized? Is there any external SNTP references or GPS Time involved? How? Exactly how?
I promote not combining Domain Controller role with any 800xA node. Keeping DCs on separate servers makes things so much simpler, not to mention backup/restore options.
The Primary and Secondary Domain may be out of Synch, try removing and adding back the secondary domain to the main domain controller.
Try removing and adding back the CS1 to domain.