Failed DC moving to backup DC not working

Home Forums Microsoft Networking and Management Services Active Directory Failed DC moving to backup DC not working

This topic contains 7 replies, has 4 voices, and was last updated by  Bharett 7 months, 2 weeks ago.

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #167524

    Migration from SBS2011 to Server 2016 Essentials
    Used this post to migrate with no problem. Everything was working. https://blogs.technet.microsoft.com/sbs/2014/02/21/deploying-windows-server-2012-r2-essentials-in-an-existing-active-directory-environment/
    The night I finished the master AD had a hardware failure and was not able to remove the master AD from Domain. I’m trying to recover the domain to the 2016 Essentials backup AD. I used this post to recover the domain:
    http://geekswithblogs.net/mhamilton/archive/2007/04/15/111674.aspx and https://www.petri.com/seizing_fsmo_roles
    Had no problem with the steps in the post. Moved to Clean up AD and used this post:
    https://www.petri.com/delete_failed_dcs_from_ad
    Next, I cleaned DNS. Deleted old DC from Name Server and replaced the old server name with a new name. Start of Authority (SOA). Check NSLOOKUP and receive this:
    1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa
    primary name server = 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa
    responsible mail addr = (root)
    serial = 0
    refresh = 28800 (8 hours)
    retry = 7200 (2 hours)
    expire = 604800 (7 days)
    default TTL = 86400 (1 day)
    Server: UnKnown
    Address: ::1
    Name: accounting-03.kkmobbs.local
    I have the same problem I started with: when I go to Active Directory Sites and Service I receive this:
    Naming information cannot be located because The specified domain either does not exist or could not be contacted.
    I’m not sure where to go from hear. This is a small domain I can start new but all the user, GPO’s and Devices where already synced so I thought it would be easier to fix this server.
    Thanks


    Ossian
    Moderator
    #191982

    Since you are getting IPv6 addresses back, there may be something up with your IPv4 stack. Have you checked the server IP is OK?


    Bharett
    Member
    #392010

    Thanks, I overlook the part of the message. I had the same problem when a set of DHCP on the server. I disabled the unused nick card in the server so I will go back and check the IP 6 on the working nick


    Bharett
    Member
    #392011

    Ossian, Thanks that fixed the DNS resolve problem, but when I go into Active Directory Sites and Services still getting “Naming Information Cannot be located…” I will rest.


    Kobe 310
    Participant
    #363146

    Try this link, someone else had the same problem and this resolved it.

    http://support.microsoft.com/kb/947022/en-us


    Bharett
    Member
    #392012

    Sorry, for the delay. Thanks, Kobe 310 I will look at the link and let you know.


    Bharett
    Member
    #392013

    Yep no Netlogon folder. Infact the SysVol folder was empty. so i guess the other dc never replicated to the new on. This link fixed that problem;
    https://social.technet.microsoft.com/Forums/en-US/b90fc0d3-a0dc-4fd9-bc4d-cf3943b07f41/sysvol-folder-is-empty?forum=winserverDS

    If i was working on a network with a lot of users and policies i would have look for another solution. This domain is very small so going back to default GPO’s was not a problem.Alluser account are still in the system. I will make GP’s.
    Thanks for all the help


    Kobe 310
    Participant
    #363147

    No problem, i’m glad to see you got it fixed!!!

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.