Windows Server 2012 Naming Information cannot be located because: The specified domain either doesn’t exist or could not be contacted. (Applicable to Windows 2016 also)

This solution works for Windows 2016 also 🙂

I met a difficult situation while setting up a DC for a new forest in Windows Server 2012 . ADDS has been setup and promoted the server as the Domain Controller for the new forest/domain. But none of the AD tools were not able to open, says a DNS error always similar to the one showed here

2012

When digging in to the machine, error messages found on the Event viewer are:

The DFS Replication service failed to contact domain controller  to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.

Additional Information:
Error: 1355 (The specified domain either does not exist or could not be contacted.)

Active Directory Domain Services was unable to establish a connection with the global catalog.
Additional Data
Error value:
1355 The specified domain either does not exist or could not be contacted.
Internal ID:
3200e24

User Action:
Make sure a global catalog is available in the forest, and is reachable from this domain controller. You may use the nltest utility to diagnose this problem.

The DFS Replication service failed to contact domain controller  to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.

Additional Information:
Error: 1355 (The specified domain either does not exist or could not be contacted.)

eDizk2w

The errors indicated that there is a problem with DFS and sysvol seems to be not accessible.

The solution seems to be very simple

Go to Registry editor and open the key SysvolReady at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

If the value of the key is 0 change it to 1. If the value is 1 change it to 0 and ‘Accept’, again change to 1 and accept. Exit registry editor.

Great !!! Worked like a charm.

 

 

149 thoughts on “Windows Server 2012 Naming Information cannot be located because: The specified domain either doesn’t exist or could not be contacted. (Applicable to Windows 2016 also)

  1. Pingback: TechNet Blogs
  2. I setup a domain controller using an eval version of Server 2012. I rolled this server out to a production environment while I waited for my server licenses to arrive.
    I soon realized that you cannot activate an eval license if you have already run DCPROMO. After demoting/promoting my server I was getting this error (among many others).
    I cannot express how happy I am that I found your blog. I was preparing to….??

  3. Worked like a charm! I was stressing out BIG time!! I followed all the steps from migrating to 2012 STD from 2003 SBS and then ran into this issue after demoting the old server. THANKS!

  4. It worked!! I worked on this issue for months! Now, the question is what did that change to 1 actually do to correct the issue.

  5. Great to hear that the article helped you to resolve an issues for months !!!!
    Definitely, it can be a bug. MS may taken care on the next patch release

  6. @ManU – I can’t help but post yet another heartfelt THANK YOU for your answer. I just wish I had found it a week ago. I’m not quite sure what the fancy wizards are good for if one still has to mess with the registry.

  7. THANK YOU ALOT!! i just did a recovery on my Win2008 Domain Controller, then it prompted the same error shown above. your solution have saved my life. thanks you

  8. Oh my LORD! I think i’m going to cry! I am soooo relieved to have found your post. Only wish i could have found it 4 hours ago! Thank you thank you from the bottom of my heart!

  9. Thank you very much for this fix! I had promoted/demoted a couple of times due to the error message, thinking I had missed a step. After double/triple checking my steps nothing was missed, and the error message still existed. Came across your fix, and BAM! Up and running.

  10. I have been using Hyper-V replicas to create a test environment. I couldn’t get the DC to actually perform as a DC. I couldn’t connect to AD DS. Made the change that you suggested and now it works.

  11. thank you thank you..
    words cannot describe my feeling now.
    just about to perform DC migration tonight, thought this issue relate to new DC was setup within current DC domain.
    I was so wrong. many thanks friends.

  12. Thanks a lot for the RegKey change.
    In our situation, we have 2012 R2 domain controller, with all FSMO roles.
    Created a replica with Veeam and put the replica in an isolated lab environment for testing.
    Nothing was working for AD DS, with the RegKey change from 0 to 1….BOOM!!!
    Great info!

  13. Greate post. Keep writing such kind of info on your page.
    Im really impressed by it.
    Hi there, You have done an excellent job. I’ll certainly digg it and personally recommend to my friends.
    I am confident they will be benefited from this website.

  14. Thank you so much.
    Spent many hours to migrate from a 2003 server to 2012R2, and after forcing unregistering the old server from the domain [dcpromo], domain was gone!!! I was desperate, imagine customer’s employees coming back from summer holiday next Sunday to a non functional environment? you just save me from big embarrassment!!!

  15. Thanks Bro.

    Bringing up a single DC on a isolated network for testing, not sure why this didn’t just work. My 2012 DC even had a different event ID 4015

  16. Yes worked. Guys in my case i had taken the backup of active directory and restored and after i was getting the above error. With this change in the registry i could get back AD.

    Wondering , how does this work ???.

    Regards,
    Siraj

  17. Yes worked. Guys in my case i had taken the backup of active directory and restored and after i was getting the above error. With this change in the registry i could get back AD.

    Wondering , how does this work ?.

    Regards,
    Siraj

  18. I have tried to dcpromo and keep getting error domain controller could not be contacted for the domain. I have tried the method that you suggested but no luck for me. The registry for the sysvol key from the primary DC is 1, anyway as you suggested if the value is 1 then change to 0. After that change it back to 1 from 0 and exit. I tried to dcpromo again and getting the same error. Any further advise? Thanks.

    1. Hi,
      Sorry to hear that you did have the issue again even after following my tips. At the same time, as you can see there are many people has shared their thought that it helped them ! Thus, I assume, your problem is something different and need more details about it so that I can help you to fix that

      Thanks,
      Manu

  19. After reading lots of webpages with almost useless guides, this finally solved problem. And it’s much easier than anything else I met before. Thanks

  20. This worked!! After restoring Xen VM, my whole domain was down and this simple fix got it up and running! Been searching for hours and couldn’t fix it! Thanks!

  21. What a dude…. I’ve been wracking my brains for hours with this and was thinking it to be with replication, even though we don’t have replication setup. I have a test environment where I took a system image of a domain controller but after a few weeks I ran into the problem. Seems to be working now, didn’t even have to restart.

    1. Thanks, I was struggling to have Win 2012 R2 BDC play the roles of the PDC for a whole day! I can now say I have a backup. Worked like charm.

  22. I thought I will be creating my domain from scratch, but this “simple” thing really works. You are awesome 🙂

  23. THANK YOU!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    You had saved my life!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

  24. I was on the left flank of Hell’s cloister about to pull the trigger, when an angel appeared with a URL to this article.

    Thanks

  25. You are a life saver and I freakin’ love you!
    I had two replicated DCs that for some reason stopped authenticating overnight and I got this message. This tip allowed me to get into AD and do what I needed to do to diagnose and get the DCs back up and running.

Leave a Reply

Your email address will not be published. Required fields are marked *

Protected by WP Anti Spam