sparkyputerguy
IS-IT--Management
Hi all-
I just finished getting everything worked out but wanted to throw this out to see if anyone had thoughts on how it started...
We've had a single domain controller up for nearly a year and this week, I decided to give it a playmate. I ran DCPROMO on a new server and configured it to be an additional DC for a new domain. All went well in terms of the wizard portion.
A day later, I checked the logs on the new server and found that it was not replicating with the first DC and that would prevent the new server from being a DC. The NTFRS service kept stopping when trying to restart it.
The specific error was ID 13549 and said that the GPT.INI file was 30 minutes newer than the time on the new server. I checked all the files from the existing server and found their created/modified dates to be a day or so older- which would make sense since they hadn't been modified for a while.
Long story short, I used NTFRSUTL to examine the out bound NTFRS data and found that although the GPT.INI file had a FirstTryTime of 1/6/04, it had an EventTime of 12/22/05. That's a little more than '30 minutes greater'!!!
The way I cleared this up was to rebuild the NTFRS database (JSI Inc. Tip# 3605). Then, neither machine wanted to be a domain controller since NTFRS withdrew the SYSVOL share on the existing server- and it had not been created on the new server... D'oh!
To fix the "lack 'o SYSVOL", I used MS KB#316790 to reset NTFRS to establish an authoritative relationship... Gotta remember to set a reg key on the non-authoritative DCs...
That worked, but all my GPs were then empty- Default Domain, Default DC, and ones I created. Luckily, I had a backup copy so I just popped them back in and all was well.
Short of someone monkeying around with my server at some point and setting the system clock to 12/22/05 (and then setting it back to current time), can anyone think of how this timestamp got there? We are not connected to any other networks, so picking up a bogus NTP setting would not have been possible.
Thanks, and have a great day!
I just finished getting everything worked out but wanted to throw this out to see if anyone had thoughts on how it started...
We've had a single domain controller up for nearly a year and this week, I decided to give it a playmate. I ran DCPROMO on a new server and configured it to be an additional DC for a new domain. All went well in terms of the wizard portion.
A day later, I checked the logs on the new server and found that it was not replicating with the first DC and that would prevent the new server from being a DC. The NTFRS service kept stopping when trying to restart it.
The specific error was ID 13549 and said that the GPT.INI file was 30 minutes newer than the time on the new server. I checked all the files from the existing server and found their created/modified dates to be a day or so older- which would make sense since they hadn't been modified for a while.
Long story short, I used NTFRSUTL to examine the out bound NTFRS data and found that although the GPT.INI file had a FirstTryTime of 1/6/04, it had an EventTime of 12/22/05. That's a little more than '30 minutes greater'!!!
The way I cleared this up was to rebuild the NTFRS database (JSI Inc. Tip# 3605). Then, neither machine wanted to be a domain controller since NTFRS withdrew the SYSVOL share on the existing server- and it had not been created on the new server... D'oh!
To fix the "lack 'o SYSVOL", I used MS KB#316790 to reset NTFRS to establish an authoritative relationship... Gotta remember to set a reg key on the non-authoritative DCs...
That worked, but all my GPs were then empty- Default Domain, Default DC, and ones I created. Luckily, I had a backup copy so I just popped them back in and all was well.
Short of someone monkeying around with my server at some point and setting the system clock to 12/22/05 (and then setting it back to current time), can anyone think of how this timestamp got there? We are not connected to any other networks, so picking up a bogus NTP setting would not have been possible.
Thanks, and have a great day!
