asked on
How can i resolve an incorrect timestamp in my sysvol folder?
I have a Windows Server 2003 network that has two domain controllers. I just added the second one a few days ago. As part of the dcpromo process, it uses FRS to copy the contents of my domain's sysvol directory from one DC to the other.
Since the dcpromo, I've been getting errors on the second DC, inculding Event ID 13549 Source Ntfrs (http://www.eventid.net/display.asp?eventid=13549&eventno=3073&source=Ntfrs&phase=1). When I look at my first domain controller's sysvol directory, the mydomain.local directory has a timestamp of 01/17/2010. The date and time on the server is correct, 10/2/2009. Both servers' times are in sync. That mydomain.local timestamp is keeping me from using FRS to my second domain controller. Any idea on how I can resolve the issue?
Since the dcpromo, I've been getting errors on the second DC, inculding Event ID 13549 Source Ntfrs (http://www.eventid.net/display.asp?eventid=13549&eventno=3073&source=Ntfrs&phase=1). When I look at my first domain controller's sysvol directory, the mydomain.local directory has a timestamp of 01/17/2010. The date and time on the server is correct, 10/2/2009. Both servers' times are in sync. That mydomain.local timestamp is keeping me from using FRS to my second domain controller. Any idea on how I can resolve the issue?
Active DirectoryWindows Server 2003
Last Comment
InterWorks
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
dcdiag from the command prompt and dcdiag/fix and restart the server.