Announcement

Collapse
No announcement yet.

Naming information cannot be located because the specified domain either does not exi

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

  • Naming information cannot be located because the specified domain either does not exi

    Two Windows Servers 2003 Standard - A and B. Server B has all FSMO roles (from Server A). After a forced replication last night, I am now getting the following error:
    Naming information cannot be located because the specified domain either does not exist or could not be contacted

    Also:

    Server A - WIndows cannot obtain the domain controller name for your computer network.
    Server B - Windows cannot query for the list of Group Policy Objects.
    Server B - Windows cannot bind to xxx.local.domain

    Server B - Event Codes 1030 and 1006 repeatedly
    Server A- Eent Codes 1054, 2114 and 2102 repeatedly

    Also:

    C:\Program Files\Support Tools>repadmin/showrepl
    repadmin running command /showrepl against server localhost
    Default-First-Site-Name\Server B
    DC Options: IS_GC
    Site Options: (none)
    DC object GUID: 62793a1f-090c-443e-b59c-535cea112c3d
    DC invocationID: 62793a1f-090c-443e-b59c-535cea112c3d
    ==== INBOUND NEIGHBORS ======================================
    DC=xxx,DC=local
    Default-First-Site-Name\SERVER B via RPC
    DC object GUID: 64d42e4d-da68-4163-85f5-91fe72964c11
    Last attempt @ 2011-01-14 09:56:03 was successful.
    CN=Configuration,DC=xxx,DC=local
    Default-First-Site-Name\Server B via RPC
    DC object GUID: 64d42e4d-da68-4163-85f5-91fe72964c11
    Last attempt @ 2011-01-14 09:56:03 was successful.
    CN=Schema,CN=Configuration,DC=xxx,DC=local
    Default-First-Site-Name\Server B via RPC
    DC object GUID: 64d42e4d-da68-4163-85f5-91fe72964c11
    Last attempt @ 2011-01-14 09:56:03 was successful.
    DC=DomainDnsZones,DC=xxx,DC=local
    Default-First-Site-Name\Server B via RPC
    DC object GUID: 64d42e4d-da68-4163-85f5-91fe72964c11
    Last attempt @ 2011-01-14 09:56:03 was successful.
    DC=ForestDnsZones,DC=xxx,DC=local
    Default-First-Site-Name\Server B via RPC
    DC object GUID: 64d42e4d-da68-4163-85f5-91fe72964c11
    Last attempt @ 2011-01-14 09:56:03 was successful

    And..........

    C:\Program Files\Support Tools>dcdiag

    Domain Controller Diagnosis

    Performing initial setup:
    Done gathering initial info.

    Doing initial required tests

    Testing server: Default-First-Site-Name\SERVER B
    Starting test: Connectivity
    ......................... SERVER B passed test Connectivity

    Doing primary tests

    Testing server: Default-First-Site-Name\ SERVER B
    Starting test: Replications
    ......................... SERVER B passed test Replications
    Starting test: NCSecDesc
    ......................... SERVER B passed test NCSecDesc
    Starting test: NetLogons
    ......................... SERVER B passed test NetLogons
    Starting test: Advertising
    Fatal ErrorsGetDcName (SERVER B) call failed, error 1355
    The Locator could not find the server.
    ......................... SERVER B failed test Advertising
    Starting test: KnowsOfRoleHolders
    ......................... SERVER B passed test KnowsOfRoleHolders

    Starting test: RidManager
    ......................... SERVER B passed test RidManager
    Starting test: MachineAccount
    ......................... SERVER B passed test MachineAccount
    Starting test: Services
    ......................... SERVER B passed test Services
    Starting test: ObjectsReplicated
    ......................... SERVER B passed test ObjectsReplicated
    Starting test: frssysvol
    ......................... SERVER B passed test frssysvol
    Starting test: frsevent
    There are warning or error events within the last 24 hours after the
    SYSVOL has been shared. Failing SYSVOL replication problems may cause
    Group Policy problems.
    ......................... SERVER B failed test frsevent
    Starting test: kccevent
    ......................... SERVER B passed test kccevent
    Starting test: systemlog
    An Error Event occured. EventID: 0x00000423
    Time Generated: 01/14/2011 09:29:47
    Event String: The DHCP service failed to see a directory server
    ......................... SERVER B failed test systemlog
    Starting test: VerifyReferences
    ......................... SERVER B passed test VerifyReferences

    Running partition tests on : ForestDnsZones
    Starting test: CrossRefValidation
    ......................... ForestDnsZones passed test CrossRefValidation

    Starting test: CheckSDRefDom
    ......................... ForestDnsZones passed test CheckSDRefDom

    Running partition tests on : DomainDnsZones
    Starting test: CrossRefValidation
    ......................... DomainDnsZones passed test CrossRefValidation

    Starting test: CheckSDRefDom
    ......................... DomainDnsZones passed test CheckSDRefDom

    Running partition tests on : Schema
    Starting test: CrossRefValidation
    ......................... Schema passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... Schema passed test CheckSDRefDom

    Running partition tests on : Configuration
    Starting test: CrossRefValidation
    ......................... Configuration passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... Configuration passed test CheckSDRefDom

    Running partition tests on : xxx
    Starting test: CrossRefValidation
    ......................... xxx passed test CrossRefValidation
    Starting test: CheckSDRefDom
    ......................... xxx passed test CheckSDRefDom

    Running enterprise tests on : xxx.local
    Starting test: Intersite
    ......................... xxx.local passed test Intersite
    Starting test: FsmoCheck
    Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
    A Global Catalog Server could not be located - All GC's are down.
    Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
    A Time Server could not be located.
    The server holding the PDC role is down.
    Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 135
    5
    A Good Time Server could not be located.
    Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
    A KDC could not be located - All the KDCs are down.
    ......................... xxx.local failed test FsmoCheck

    Needless to say, first time post here and need assistance desperately, I appreciate all the detailed help I can get to resolve this as soon as possible. Clients are still able to log in.

  • #2
    Re: Naming information cannot be located because the specified domain either does not

    Appears to be nothing to do with SBS so moved to Server forum
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: Naming information cannot be located because the specified domain either does not

      have you tried dcdiag /fix ?

      Also - make sure all your servers ARE global catalogs, and check your DNS SRV Records.
      Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

      Comment


      • #4
        Re: Naming information cannot be located because the specified domain either does not

        NETDIAG is posted above previously.

        Also, Server A has the SYSVOL shared whereas Server B does not. Server A seems to have all the files needing to be in SYSVOL whereas Server B has empty files in SYSVOL

        Hope that helps

        Server A - IPCONFIG

        Windows IP Configuration
        Host Name . . . . . . . . . . . . : Server A
        Primary Dns Suffix . . . . . . . : xxx.local
        Node Type . . . . . . . . . . . . : Hybrid
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : xxx.local
        Ethernet adapter internal:
        Connection-specific DNS Suffix . :
        Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Dual Port Network Co
        nnection #2
        Physical Address. . . . . . . . . : 00-07-E9-06-EE-6E
        DHCP Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 10.1.xxx.xx5
        Subnet Mask . . . . . . . . . . . : 255.255.xxx.xxx
        Default Gateway . . . . . . . . . : 10.1.x.x
        DNS Servers . . . . . . . . . . . : 10.1.xxx.xx5
        10.1.xxx.xx6
        NetBIOS over Tcpip. . . . . . . . : Disabled


        Server B

        Windows IP Configuration
        Host Name . . . . . . . . . . . . : Server B
        Primary Dns Suffix . . . . . . . : xxx.local
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No
        DNS Suffix Search List. . . . . . : ixxx.local
        Ethernet adapter Local Area Connection 2:
        Connection-specific DNS Suffix . :
        Description . . . . . . . . . . . : Intel(R) PRO/1000 PM Network Connection
        Physical Address. . . . . . . . . : 00-25-90-14-3C-D0
        DHCP Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 10.1.xxx.xx6
        Subnet Mask . . . . . . . . . . . : 255.255.xxx.xxx
        Default Gateway . . . . . . . . . : 10.1.x.x
        DNS Servers . . . . . . . . . . . : 10.1.xxx.xx6
        10.1.xxx.xx5
        NetBIOS over Tcpip. . . . . . . . : Disabled

        Comment


        • #5
          Re: Naming information cannot be located because the specified domain either does not

          no, netdiag is not posted above. DCDIAG is.
          And that doesn't tell me you ran it with /FIX

          And what it DOES tell me is that several steps in that DCDIAG failed because it cannot locate Domain Controller, or Global Catalog entries.

          What THAT suggests to me is that there could be a problem with your dns environment (IE, Active Directory 101: DNS is crucial)

          So what I would personally do next, is go and look at the DNS records - specifically the LDAP SRV records, and make sure that they are all correct and inplace. I'd probably also try re-register commands.

          Of course, that's just what I'd do if it was me.

          Other people would post on a forum, then proceed to ignore suggestions.





          One of the critical questions, that may actually help us help you:
          WHY did you force replication? What bought on the need to do this?
          Last edited by tehcamel; 15th January 2011, 13:01.
          Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

          Comment


          • #6
            Re: Naming information cannot be located because the specified domain either does not

            Here is NETDIAG - thought I had posted it - simple MISTAKE:

            NETDIAG:
            AutoConfiguration results. . . . . . : Passed

            Default gateway test . . . : Passed


            WINS service test. . . . . : Skipped
            NetBT is disable on this interface. [Test skipped].


            Global results:


            Domain membership test . . . . . . : Failed
            [WARNING] Ths system volume has not been completely replicated to the local
            machine. This machine is not working properly as a DC.


            NetBT transports test. . . . . . . : Skipped
            There are no interfaces that have NetBT enabled. [Test skipped]


            Autonet address test . . . . . . . : Passed


            IP loopback ping test. . . . . . . : Passed


            Default gateway test . . . . . . . : Passed


            NetBT name test. . . . . . . . . . : Skipped
            There are no interfaces that have NetBT enabled. [Test skipped]


            Winsock test . . . . . . . . . . . : Passed


            DNS test . . . . . . . . . . . . . : Passed
            PASS - All the DNS entries for DC are registered on DNS server '10.1.x.xxx'
            and other DCs also have some of the names registered.
            PASS - All the DNS entries for DC are registered on DNS server '10.1.x.xxx'
            and other DCs also have some of the names registered.


            Redir and Browser test . . . . . . : Skipped
            There are no interfaces that have NetBT enabled. [Test skipped]


            DC discovery test. . . . . . . . . : Failed
            [FATAL] Cannot find DC in domain 'xxx'. [ERROR_NO_SUCH_DOMAIN]


            DC list test . . . . . . . . . . . : Failed
            'xxx': Cannot find DC to get DC list from [test skipped].


            Trust relationship test. . . . . . : Skipped


            Kerberos test. . . . . . . . . . . : Skipped
            'xxx': Cannot find DC to get DC list from [test skipped].


            LDAP test. . . . . . . . . . . . . : Failed
            Cannot find DC to run LDAP tests on. The error occurred was: The specified d
            omain either does not exist or could not be contacted.

            [WARNING] Cannot find DC in domain 'xxx'. [ERROR_NO_SUCH_DOMAIN]


            Bindings test. . . . . . . . . . . : Passed


            WAN configuration test . . . . . . : Skipped
            No active remote access connections.


            Modem diagnostics test . . . . . . : Passed

            IP Security test . . . . . . . . . : Skipped

            Note: run "netsh ipsec dynamic show /?" for more detailed information


            The command completed successfully

            ---------

            I have checked the DNS settings prior to posting. Other people would post on a forum, then proceed to ignore suggestions -I'm not "other people" so that tidbit of info does not concern me nor the problem I am having nor does it help resolve my issue.

            Just looking for help in resolving my issue, not someone's opinion on forum etiquette

            Thanks

            Comment


            • #7
              Re: Naming information cannot be located because the specified domain either does not

              Originally posted by renniscom View Post

              I have checked the DNS settings prior to posting. Other people would post on a forum, then proceed to ignore suggestions -I'm not "other people" so that tidbit of info does not concern me nor the problem I am having nor does it help resolve my issue.
              you see, when people volunteer their time on forums, they aren't mind readers. So they don't know, for instance, that someone has already checked DNS, if they haven't been told.

              I still think a critical question that you need to ask and answser (if only for yourself) is WHY did you need to force replication?


              Have you google results on any of those error outputs given you any information that helps? I've found several things that could be helpful, (especially now combined with your latest netdiag output)

              you want "detailed help" to get this resolved quickly - yet you're not giving us detailed information, and appearing to ignore, or not acknowledge, suggestions.


              what about netdiag /fix and dcdiag /fix

              have you tried either of those switches?


              why don't you tell us exactly what you've done so far, so we understand what we're trying to troubleshoot. The reason I need to ask things like "have you checked DNS" is because I DON'T KNOW that you've done it. And the reason I needed to push the issue again, is because YOU DIDN'T TELL ME when I prompted you.
              Last edited by tehcamel; 15th January 2011, 13:35.
              Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

              Comment


              • #8
                Re: Naming information cannot be located because the specified domain either does not

                Just to keep "in the loop" whoever needs assistance on this as well as in the future, the issue was not dns but the sysvol and netlogon files not being shared. Used linkd.exe to remedy this issue.

                Other than getting "schooled" on forum etiquette here for some particular reason, the advice given was good to check and rule out but not the only reason this issue can occur on a server.

                Thanks

                Comment

                Working...
                X