Only boots in to AD recovery

Discussion in 'Active Directory' started by Deb, Jul 23, 2009.

  1. Deb,

    What also is confusing me, is that you have a zone called
    "jlfsrv.jlfsrv.workstations.jlfisher.local," but there is a server
    jlfsrv.jlfsrv.workstations.jlfisher.local in it. Is that the one you can't
    get into?

    Does the zone, "jlfsrv.workstations.jlfisher.local" actually exist in DNS?

    Ace Fekay [MCT], Jul 25, 2009
    1. Advertisements

  2. Deb

    Deb Guest

    Thank you all for your help.
    Will post Monday how this was all fixed.
    And what can happen when you do a boot from CD repair of an DC.
    Need to get all the note together.
    Thank you again,

    Deb, Jul 26, 2009
    1. Advertisements

  3. You are welcome. Looking forward to your report.

    Ace Fekay [MCT], Jul 26, 2009
  4. Hello Deb,

    Let's wait for monday. You can not repair a domain form the installation
    disk, you maybe able to recover the server OS and the Domain services role,
    but not the forest/domain itself, this requires a AD aware backup.

    Best regards

    Meinolf Weber

    Meinolf Weber [MVP-DS], Jul 26, 2009
  5. Hello Meinolf,

    I have been following your reply to Deb's post. I also have similar problem
    with my AD forest domain. In my case, the AD database of my forest/root
    domain server is corrupted and I don't have a system state backup of the
    forest/root server. I know the AD database is corrupted because when I boot
    up the server normally it gets to a point saying "rebuilding Active
    Directory indices..." but it fails to complete the AD rebuilding. It then
    displays an error message saying "Directory Service cannot start.....", it
    then suggest that I should try starting the server in Active Directory
    Restore Mode.
    I am able to start the forest /root server in AD restore mode and tried all
    the database recovery steps and commands from TechNet but still can't fix
    the problem. I know my last option is to reinstall the server since I don't
    have a system state backup for the restore process. But am scared to do this
    because I don't want to lose my child domain servers functionalities and
    connections to the forest domain. My child domain servers are responsible
    for authentication of all computer and user accounts on the network. All
    users on the domain still can logon to the domain and carry out domain tasks
    even with the forest domain server offline.

    My question is if I reinstall the forest domain server, will I lose the
    connection and functionality of my child domain server which is working
    "fine" presently. Secondly, will domain applications that depends on some
    functionalities of the schema and domain naming master roles (held present
    by my faulty forest/root server) continue to function properly. Thirdly, is
    there any way I can repair the server.

    My AD domain/server setup is as follows:
    - Forest/Parent Domain:
    - Child Domain: &

    Please any help will be appreciated.

    Kingsley Akhimien, Jul 27, 2009
  6. Hello Kingsley,

    Please create a new posting with the same content. This one lets use only
    for Deb. If we jump into your problem here it is becoming too large and confusing
    to follow it.

    Best regards

    Meinolf Weber
    Meinolf Weber [MVP-DS], Jul 27, 2009
  7. Deb

    Deb Guest

    Sorry for the delay have been rebuilding the file server.

    This all started due to the battery on the motherboard going out. Once
    replaced someone (not me) ran repair system from CD due to the boot file
    becoming corrupt I was told. This does not repair a DC in a good way. So the
    lack of backups to restore the child domain a rebuild is the only way. Yes I
    did figure out it was a child domain with no backup DC. But it did leave the
    primary Domain unable to register DNS records.

    -Checked the roles of the dc and found that there were no support tools so
    installed support tools and saw the dc fisher.local had all the fsmo roles
    -Then stopped the frs service and then went to
    And then on cumulative replica did D4 and then started frs service
    -The error for 13568 in event viewer was gone
    -Then ran dcdiag/q and saw the errors were all fine
    -Then checked the dns bindingon dc and saw that the binding was incorrect
    so corrected it
    -Then saw that on TCP-IP properties on the DNS tab “Register this dns was
    not checked" so checked the same and then the records were registered in the
    dns for the dc
    -Clent “jlfsrv1" was not able join to the domain though it was pinging
    through its ip address and hostname so configured the ip address of the
    client machine and pointed it to the dc and then did ipconfig /flushdns and
    ipconfig /registerdns and then went to dsa.msc and in computers the new
    machine was joined “jlfsrv1".
    -Issue resolved

    This is a reminder to me to go back to the basics “Keep It Simpleâ€

    Buy the way the workstations object in DNS has been removed due to it made
    no since to have it with only one network and on subnet.

    Deb, Jul 30, 2009
  8. Hello Deb,

    No problem, recovery takes time. So if i got you correct you are up and running
    again, then Congratulations. :)

    Best regards

    Meinolf Weber

    Meinolf Weber [MVP-DS], Jul 30, 2009

  9. [snipped]

    I agree with Meinolf. Good to hear you got it working!

    Ace Fekay [MCT], Jul 31, 2009
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.