Question

  • Creator
    Topic
  • #2160235

    Windows Cannot obtain the domain controller name for your computer network.

    Locked

    by miketkelly ·

    I’ve been having a problem with one of my client computers. Every time the computer logs onto the domain this error is logged.
    ============================
    Event ID: 1054
    Source: Userenv
    User: NT AUTHORITY/SYSTEM
    Description:
    Windows Cannot obtain the domain controller name for your computer network. (An unexpected network error occurred.) Group Policy processing aborted
    ============================

    on the domain controller I get two entries into the security log with the user being the client computer name

    first this one-
    Event ID: 540
    Source: Security
    Category: Log on / Log off
    Successful Network Log on:
    username: (client computer name)
    logon type: 3
    Logon Process: Kerberos
    Authentication Package: Kerberos

    the second one is rather long but the category is Directory Service Access

    If anyone could help me get through this that would be fantastic and your help would be greatly appreciated.

All Answers

  • Author
    Replies
    • #2755004

      Clarifications

      by miketkelly ·

      In reply to Windows Cannot obtain the domain controller name for your computer network.

      Clarifications

    • #2755003

      Have you tried

      by w2ktechman ·

      In reply to Windows Cannot obtain the domain controller name for your computer network.

      removing the computer from the domain and re-adding it?

      • #2754987

        I have

        by miketkelly ·

        In reply to Have you tried

        re-added once already
        is there something I can test on the server to ensure it is setup correctly for logging on or is this an issue with the client

        • #2754974

          If the other systems are

          by w2ktechman ·

          In reply to I have

          working properly, and this system is not, more than once, it is likely the install or a service has failed.
          What happens with a re-install of the OS?

        • #2754930

          I may

          by miketkelly ·

          In reply to If the other systems are

          have to give that a shot

    • #2754972

      See if this will help

      by rob miners ·

      In reply to Windows Cannot obtain the domain controller name for your computer network.

      Testing and Resetting the Secure Channel

      Check this link

    • #2754744

      Try…

      by maex ·

      In reply to Windows Cannot obtain the domain controller name for your computer network.

      …this…
      I would go about it like so…

      Do a NSLOOKUP on your DC from the PC.

      Telnet your AD on your DC from that PC.

      If something is strange, would delete machine account from AD, and put PC in workgroup mode and verify network settings. Check Netbios, usually is on Default.

      Join the AD, from the PC.

      • #2767833

        i tried

        by miketkelly ·

        In reply to Try…

        doing nslookup server00-dc and these are my results

        *** Can’t find server name for address 172.20.1.117: Non-existent domain
        *** Default servers are not available
        Server: UnKnown
        Address: 172.20.1.117

        Name: server00-dc.
        Address: 172.20.1.117

        I also tried my secondary DC (server01-db)

        *** Can’t find server name for address 172.20.1.117: Non-existent domain
        *** Default servers are not available
        Server: UnKnown
        Address: 172.20.1.117

        Name: server01-db.
        Address: 172.20.1.118

        is this telling to anyone

        I also tried taking the client pc off the domain changing the computer name and rejoining the domain

        Thanks for all the suggestions so far

      • #2767012

        found some new information

        by miketkelly ·

        In reply to Try…

        I was using FRSDiag.msi to check out some of the problems

        would the fact that my current server’s (server00-dc) member name is the old computer name (VISION-1E30CAA5) have anything to do with the problem I’m having

        I had actually completely forgot that this server’s name was changed until I saw this

        =================================================
        Replica Set GUID: 96a3551d4e96-4cod-a0145f5b51fd22226
        Replica Set Name : DOMAIN SYSTEM VOLUME (SYSVOL SHARE)
        ======================================================
        GUID_________MEMBERNAME__________SERVER NAME
        ——————————————————————————————————–
        #######______SERVER01-DB___________server01-db
        #######______VISION-1E30CAA5________server00-dc
        ======================================================

        =============================================
        Replica Set GUID: ######################
        Replica Set Name: DFS Network Share
        =============================================

    • #2766979

      This looks strangely familiar

      by seanferd ·

      In reply to Windows Cannot obtain the domain controller name for your computer network.

      Something about being unable to apply gp when no when no one is logged on or some other reason.

      Local Policy:
      Computer\Administrative Templates\System\Logon\[Always wait for the network at computer startup and logon]

      I had to mess with this when I was given a computer that was pulled right off a domain and given away when Stupid Wasteful Bank was upgrading.

      Anyway, it’s somewhere to look.

    • #2778199

      Perhaps Its Your Time-Stamp Counter

      by don19 ·

      In reply to Windows Cannot obtain the domain controller name for your computer network.

      A post on Microsoft says:

      This problem occurs when the time-stamp counters for different processor cores are not synchronized. Windows Server 2003 uses the time-stamp counter as a timekeeping source. Each processor contains a time-stamp counter.

      To resolve this problem, configure Windows Server 2003 to use the PM_TIMER setting instead of the time-stamp counter. To do this, add the /usepmtimer parameter to the Boot.ini file, and then restart the server.

      Note that the /usepmtimer parameter is automatically added to the Boot.ini file when you install the latest AMD PowerNow! Technology driver from AMD. The updated driver itself does not resolve this problem. However, the installation process makes the necessary changes to the Boot.ini file to resolve this problem.

    • #2840015

      Dear friend

      by ashishpatel ·

      In reply to Windows Cannot obtain the domain controller name for your computer network.

      frist check your network settings using admiitrator account i think there is some problem with your network…..

      Ashish Patel

Viewing 6 reply threads