B
Bob Mase
All,
I had a situation where Tardis was used to sync the time
on the domain Controllers. Tardis hit a bad Time server
on the Internet causing the Server clock to spin out of
control, ( it would advance the time at a rate that would
go through 24 hours in about 5 seconds)
Now after that has been resolved, the Domain won't
replicate correctly. If I force a replication in AD Sites
and Services, I can replicate from the server that had
the problem to the servers that did not, but not from the
servers to the server that had the problem w/Tardis.
The error message that I get is as follows;
"The following error occurred during the attempt to
syncronize the domain controller:
Access is Denied."
I have looked at the knowledge base and can not find this
specific situation; has anyone out there seen this and
what was the fix?
Any assistance would be appreciated!
Best regards,
Bob
I had a situation where Tardis was used to sync the time
on the domain Controllers. Tardis hit a bad Time server
on the Internet causing the Server clock to spin out of
control, ( it would advance the time at a rate that would
go through 24 hours in about 5 seconds)
Now after that has been resolved, the Domain won't
replicate correctly. If I force a replication in AD Sites
and Services, I can replicate from the server that had
the problem to the servers that did not, but not from the
servers to the server that had the problem w/Tardis.
The error message that I get is as follows;
"The following error occurred during the attempt to
syncronize the domain controller:
Access is Denied."
I have looked at the knowledge base and can not find this
specific situation; has anyone out there seen this and
what was the fix?
Any assistance would be appreciated!
Best regards,
Bob