DCPROMO lead to time related error.

[Bob Zabaga]

After running DCPROMO on my server, I was required to
reboot. Upon reboot, I couldn't log in to my new domain
controller because of a "time/date not synchronized
between server and client error". I've had that happed
between an end-user PC and a DC, but not with a server I
just promoted to a domain controller.

The only way I can login to my new DC is to go into
F8 "directory services restore mode" (aka safe mode). Then
I can login and look for clues...

From here, I went to the command prompt and ran "net
time /domain:name_here /set" but that returned an error 5
which is an access denied message.

During DCPROMO, there were no errors. In checking the
event viewer on both DCs I have and found little
error/warnings. I do see an "mrxsmb error 3034".

Any help would be great. Thanks all.

-bobz

 

[Guest]

Is this the first DC in the domain or an additional DC?
Im going to try and answer you based upon it being an additional DC.
Boot into DS restore mode and confirm that the Date, Time, and Time zone are
correct and compare to any other existing DCs.
The Kerberos protocol will fail if there is a time skew greater than 5 min,
as a security precaution.

If this is the only DC you might want to investigate and see if there is any
discrepency between event logs and the current system time. The only way I
could see this occur on a single DC would be if the system time was set to a
period that was before the DC was promoted.