Windows Server 2012 Naming Information cannot be located because: The specified domain either doesn’t exist or could not be contacted

We 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.
Posted by
Labels:

17 comments:

  1. UnknownFebruary 25, 2019 at 3:47 AM

    you are great

    ReplyDelete
  2. UnknownDecember 14, 2019 at 10:28 PM

    Thank you, I've been struggling with this for a day now!

    ReplyDelete
  3. AnonymousJune 15, 2020 at 10:52 AM

    Thanks Alooot

    ReplyDelete
  4. Latest Bollywood MoviesJuly 9, 2020 at 12:02 AM

    excellent and works

    ReplyDelete
  5. pranay vanjareJuly 29, 2020 at 8:14 PM

    Superb, It's really deep dig R & D

    ReplyDelete
  6. trestSeptember 21, 2020 at 1:27 PM

    work! thank you

    ReplyDelete
  7. AnonymousOctober 28, 2020 at 7:06 AM

    thanks you bro

    ReplyDelete
  8. UnknownNovember 22, 2020 at 6:09 PM

    Very much appreciated!

    ReplyDelete
  9. Agboola koladeDecember 15, 2020 at 3:12 AM

    you are a life safer, thanks alot

    ReplyDelete
  10. Essiet VictorDecember 31, 2020 at 10:55 AM

    Pls which of them under parameter are you changing to 1 or 0 bcus there are many items under parameter

    ReplyDelete
  11. AnonymousJanuary 8, 2021 at 9:04 PM

    Awesome! I was pulling my hair out until find this. My scenario is a DC replicated in a cloud for sanbox testing, so, I have to seize roles and then, the AD users and computers tool stop working. I initially think that this was because the DC cannot contacted the others DCs in forest.

    ----
    Genial! estuve rompiendome la cabeza unos dias, me habia dejado de andar la tool de AD users and computers. Mi escenario es una replica del DC en la nube para testing, entonces pensé que era problema de que el DC no contactaba el forest aun cuando hice el seize de los roles, pero no, era todo del registro el asunto (y eso que los errores hablaban del DNS!).

    ReplyDelete
  12. Ahmad khatibJuly 11, 2021 at 5:20 PM

    thank you thank you thank you thank you thank you thank you
    thanks a million

    ReplyDelete
  13. AhmefOctober 27, 2021 at 2:58 AM

    Thanks

    ReplyDelete
  14. UnknownNovember 10, 2021 at 9:54 PM

    (y)

    ReplyDelete
  15. AnonymousMay 17, 2022 at 11:29 AM

    Very Very Nice

    ReplyDelete
  16. AnonymousNovember 10, 2022 at 5:33 PM

    You are great man

    ReplyDelete

Subscribe to: Post Comments (Atom)