Announcement

Collapse
No announcement yet.

"The Specified domain controller could not be contacted"

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • "The Specified domain controller could not be contacted"

    Our AD site contains 3 DC's: 2 at head office and 1 at a branch office.

    At our branch office, when I attempted to launch Group Policy Management Console, it will give me an error saying:
    "The specified domain controller could not be contacted. This affects all sites in the console for the following forest."

    I ran DCDiag and the error that appeared was the following:
    Running enterprise tests on : domain.local
    Starting test: LocatorCheck
    Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
    A Primary Domain Controller could not be located.
    The server holding the PDC role is down.
    I ran dcdiag on the domain controller at the head office and it passed without any issues. I can perform a nslookup of the DC, ping the DC and even share files between the servers without any issues.

    Any idea how to fix this?

  • #2
    Re: "The Specified domain controller could not be contacted"

    Firewall between the remote and main office? If so, you may need to open additional ports to allow traffic between the sites.

    If you have access to the firewall logs, a quick check of the logs will show whether or not traffic is being dropped between the source and target systems.
    JM @ IT Training & Consulting
    http://www.itgeared.com

    Comment


    • #3
      Re: "The Specified domain controller could not be contacted"

      also check and see if the domain controller actually is down at all. Check the services. Services fail for unknown reasons sometimes, so it's worth checking.

      Comment

      Working...
      X