none
Error: The specified domain either does not exist or could not be contacted.

    Question

  • I see other people have had this error.  I just started getting the error and the answers other got in this forum don't exactly fit my situation.  Here's the problem:

     

    I have a Windows 2003 SP2 server that is my primary DC.  This same server is also my DNS and WINS server.  When I try to open the Group Policy Management Console from from this server, I get the error "The specified domain either does not exist or could not be contacted."  I get three choices of what to do 1) Choose a different domain controller, 2) Retry, 3) Remove all sites in this forest from the console.  I chose option 1 for "Choose a different domain controller", then I click Cancel and then Group Policy Management opens up.  I can't seem to find out how to get rid of this error.  Also, I am unable to backup directory services as well, I'm assuming due to this error.  I haven't made any changes to AD, so I don't know why I'm getting this all the sudden when it has been running fine for years.

    Wednesday, October 19, 2011 7:37 PM

Answers

  • Thanks everyone for your help.  I found the issue.  I had a misbehaving Samba server running on Linux that was trying to be the PDC.  Once I fixed the issue on the Samba server, my problems went away.
    • Marked as answer by Mike Vierling Thursday, October 20, 2011 7:04 PM
    Thursday, October 20, 2011 7:04 PM

All replies

  • How many DCs do you have?  Please post IPCONFIG/ALL from this DC.


    Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+| Houston, TX
    Blogs - http://blogs.sivarajan.com/

    FaceBook Twitter LinkedIn SS Tech Forum

    This posting is provided AS IS with no warranties,and confers no rights.
    Wednesday, October 19, 2011 7:38 PM
  • Hi,

    please verify your dns configuration.

    Like Santhosh wrote please post an unedit ipconfig -all form the server.

    You can also run the following test and upload the result to skydrive.

    dcdiag /v /c /d /e /s:dcname >c:\dcdiag.txt


    Martin Forch
    Wednesday, October 19, 2011 8:54 PM
  • Hello,

    that should be a DNS resolution problem.

    Please make sure that:

    • Each DC / DNS server points to its private IP address as primary DNS server and other internal DNS servers as secondary ones
    • Each DC without DNS pints to internal DNS servers as DNS servers
    • Each DC has just one IP address
    • Each public DNS server is set as a forwarder and not in IP settings

    Once done, run ipconfig /registerdns and restart netlogon on each DC you have.

    For client computers, please make them points to internal DNS servers as primary and secondary DNS servers.

     


    This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

    Microsoft Student Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator: Security
    Microsoft Certified Systems Engineer: Security
    Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist: Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise Administrator
    Microsoft Certified IT Professional: Server Administrator
    Microsoft Certified Trainer

    • Proposed as answer by Abhijit Waikar Thursday, October 20, 2011 3:12 AM
    Wednesday, October 19, 2011 9:15 PM
  • Hello,

    as already mentioned, one main problem maybe DNS so then ipconfig /all is the first we should check here to exlcude this. Also you may have problems between the DCs so please upload the following files:

    dcdiag /v /c /d /e /s:dcname >c:\dcdiag.txt
    repadmin /showrepl dc* /verbose /all /intersite >c:\repl.txt  ["dc* is a place holder for the starting name of the DCs if they all begin the same (if more then one DC exists)]
    dnslint /ad /s "DCipaddress" (http://support.microsoft.com/kb/321045)


    As the output will become large, DON'T post them into the thread, please use Windows Sky Drive (skydrive.live.com) [with open access!] and add the link from it here. Also the /e in dcdiag scans the complete forest, so better run it on COB.


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Thursday, October 20, 2011 5:27 AM
  • I have three DCs total.  This one is the primary.  Here is the ipconfig /all data:

     

     

    Windows IP Configuration

     

       Host Name . . . . . . . . . . . . : EXCHANGE

       Primary Dns Suffix  . . . . . . . : bgbc.local

       Node Type . . . . . . . . . . . . : Hybrid

       IP Routing Enabled. . . . . . . . : No

       WINS Proxy Enabled. . . . . . . . : No

       DNS Suffix Search List. . . . . . : bgbc.local

     

    Ethernet adapter Local Area Connection 2:

     

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection #2

       Physical Address. . . . . . . . . : 00-11-43-E6-AE-40

       DHCP Enabled. . . . . . . . . . . : No

       IP Address. . . . . . . . . . . . : 192.168.1.40

       Subnet Mask . . . . . . . . . . . : 255.255.255.0

       Default Gateway . . . . . . . . . : 192.168.1.2

       DNS Servers . . . . . . . . . . . : 192.168.1.40

       Primary WINS Server . . . . . . . : 192.168.1.40

     

    Ethernet adapter Connection to Lefthand SAN:

     

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection

       Physical Address. . . . . . . . . : 00-11-43-E6-AE-3F

       DHCP Enabled. . . . . . . . . . . : No

       IP Address. . . . . . . . . . . . : 172.16.1.40

       Subnet Mask . . . . . . . . . . . : 255.255.255.0

       Default Gateway . . . . . . . . . :

     

    Thursday, October 20, 2011 1:47 PM
  • Hello,

    according to the name EXCHANGE the server seems to have Exchange installed which is not recommended doesn't matter which version, even not from Microsoft.

    http://technet.microsoft.com/en-us/library/aa997407(EXCHG.80).aspx

    http://msmvps.com/blogs/acefekay/archive/2009/08/08/moving-from-exchange-2000-currently-on-a-windows-2000-domain-controller-to-a-new-exchange-2003-server-on-a-windows-2003-member-server.aspx

    Also the DC is multi-homed, more then one ip address is used, which result in multiple problems. Please remove the second ip address, clear DNS zones form this one also, and run ipconfig /flushdns and ipconfig /registerdns and restart the netlogon service on the DC.

    Still missing the ipconfig /all from the other DCs.


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Thursday, October 20, 2011 2:35 PM
  • Hello,

    there are connectivity problems between the DCs, which is also shown in the dcdiag output, as they seem to not be correct registered in DNS zones:

    Summary of DNS test results:
            
                                                Auth Basc Forw Del  Dyn  RReg Ext 
                   ________________________________________________________________
                    Domain: bgbc.local
                   dcbackup                    PASS PASS n/a  n/a  n/a  PASS n/a 
                   bgbc-svr2                   PASS PASS n/a  n/a  n/a  FAIL n/a 
                   EXCHANGE                 PASS PASS PASS PASS PASS FAIL n/a

     

    Is the DHCP client service started and set to automatic, as this is required for correct DNS registration?

    Any firewall between the DCs, the make sure to follow: http://technet.microsoft.com/en-us/library/dd772723(WS.10).aspx

    But the main problem seems to be the multi-homing of the DCs.


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Thursday, October 20, 2011 2:39 PM
  • The Exchange server has two nics.  One is for the backbone for ISCSI SAN traffic, the other for network use.  I realize it isn't recommended to have Exchange installed, but it has been like that for years, and it worked fine.  Windows server small business uses the exact same configuration and they support that.  Uploading other DC's ipconfig /all to skydrive and will post links when finished.  Thanks!
    Thursday, October 20, 2011 2:42 PM
  • Here is the skydrive link to all the files (dcdiag.txt, plus the three ipconfig /all results from each dc):

     

    https://skydrive.live.com/redir.aspx?cid=a69227be23869123&resid=A69227BE23869123!132

     

    Thursday, October 20, 2011 2:47 PM
  • The Exchange server has two nics.  One is for the backbone for ISCSI SAN traffic, the other for network use.  I realize it isn't recommended to have Exchange installed, but it has been like that for years, and it worked fine.  Windows server small business uses the exact same configuration and they support that.  Uploading other DC's ipconfig /all to skydrive and will post links when finished.  Thanks!


    Hello,

    SBS version is independent from the regular Windows versions and especially made for multi-homing configuration. If you still have the need for multi-homed systems, please follow exactly the way described from Ace Fekay:

    http://msmvps.com/blogs/acefekay/archive/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters.aspx


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Thursday, October 20, 2011 2:51 PM
  • Hello,

    the ipconfig look okay so far, beside the multi-homing part.

    What about the open questions?


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Thursday, October 20, 2011 2:52 PM
  • I have two network cards, each with one tcpip address.  One network card connect to the iSCSI Lefthand SAN (for storage) and the other network card is regular network we connect to for access.  This setup has worked for years and suddenly I am unable to backup active directory and get that error, I posted in my first post, when I try to open group policy
    Thursday, October 20, 2011 3:00 PM
  • dnslint and repadmin files have been uploaded to skydrive link
    Thursday, October 20, 2011 3:28 PM
  • Hello,

    what about the open questions:

    "Is the DHCP client service started and set to automatic, as this is required for correct DNS registration?

    Any firewall between the DCs, the make sure to follow: http://technet.microsoft.com/en-us/library/dd772723(WS.10).aspx"


    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
    Thursday, October 20, 2011 3:29 PM
  • Yes, DHCP client service is set to automatic.  No, there is no firewall between the DCs.  I do get the following error in the system log in the event viewer:

    The name "BGBC       1b:" could not be registered on the Interface with IP address 172.16.1.40.  The machine with the IP address 192.168.1.40 did not allow the name to be claimed by this machine.

     

    Both those IPs (172.16.1.40 & 192.168.1.40) are on the same machine (Exchange) which is the primary DC.  The first IP is assigned one nic for the SAN backbone and the other IP is assigned to a different nic for regular use.

    Thursday, October 20, 2011 3:47 PM
  • Thanks everyone for your help.  I found the issue.  I had a misbehaving Samba server running on Linux that was trying to be the PDC.  Once I fixed the issue on the Samba server, my problems went away.
    • Marked as answer by Mike Vierling Thursday, October 20, 2011 7:04 PM
    Thursday, October 20, 2011 7:04 PM
  • Hi Mike,

     

    Glad to hear that the issue has been resolved. Thanks for your feedback and sharing. Your time and efforts are highly appreciated.

     

    Best Regards,

    Nina


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Friday, October 21, 2011 7:22 AM
    Moderator