Hello, I have two 2003 SP2 x86 domain controllers. One crashed, I tried to repair but no can do!Reinstalled and the restored system disk and system state successfully.Restarted server normally (this was not an authoriative restore)Server restarted ok. I could log in.But could not se any ordinary AD tools such as sites and services or ADUC.Installed the tools manually. Wheen tools was installed and tried to open the ADUC I received the error message "naming information cannot be located because the target principal name is incorrect".But after a while this "solved itself". So it seems anyway, for now I am able to open ADUC and see the "correct" AD info. I do see all users, computers and OU's made by mee.But there is something wrong, if I feks run the tool netdiag /test:dns. All tests pass except the "most important one" about the sysvol. I receive the error message [warning] The system volume has not been completely replicated to the local machine. This machine is not working properly as a DC."I have looked into these two links:http://searchwindowsserver.techtarget.com/tip/0,289483,sid68_gci1320325_mem1,00.htmlhttp://support.microsoft.com/kb/315457I amafraid to try the "forcing SYSVOL replication, using KB 290762 -- setting BURFLAGS value on the PDC to D4 and on the other DC to D2 --" in case I will wipe out SYSVOL on the only remaing woriking DC.I also looked up som "fixes" on the error about the "naming information cannot be located because the target principal name is incorrect". This implies that the computer account domian password needs to be reset?http://support.microsoft.com/kb/325850Could this be the case?I have "off course" had problems with my backup routine the last two months as well. No problems come alone! Therefore the last successfull backup I had of the crashed DC was from the 1st of BNovember 2009. We have not altered on the Tombstone value, so it should be no problems with that. Since it is less than 60 days since that backup was restored.Could you please recomend what to do in order to get this DC up and running?Best reagrdsMorten Fredrik

Hello Friend :If i am right you had two domain controllers one acts as primary and the other acts as the secondary !! one of them crashed so you have one of them right now ? In this case i recommnad to reinstall the windows 2003 server , Seize the crashed DC from the secondary DC and create a new additional DC usning the new one .Network is my LOVE

Hi, To better understand the issue, please collect MPSReport on both domain controllers:1. Download MPSReport from the following linkhttp://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd915706/MPSRPT_DirSvc.EXE2. Double-click the executable to launch the report gathering tool on the domain controllers.3. After the tool finishes gathering the information, you wil see a .cab file in C:\WINDOWS\MPSReports\DirSvc\cab folder. Please upload the .cab file to the following space: https://sftasia.one.microsoft.com/choosetransfer.aspx?key=9b01e782-f89a-4d65-bb70-47df65835473 Password: tsid6gw1uOOCTThis posting is provided "AS IS" with no warranties, and confers no rights.

Hi,How's everything going? I've not heard back from you in a few days and wanted to check the current status of the issue. If you need any further assistance, please feel free to respond back.Thanks.This posting is provided "AS IS" with no warranties, and confers no rights.