Windows cannot obtain the Domain Conroller Name....

Discussion in 'Windows Networking' started by SP, Jul 14, 2004.

  1. SP

    SP Guest

    Hello,

    We recently upgraded from Win NT 4.0 to Windows 2003 and
    although out network appears to be working fine our
    client PCs (W2K & XP) receive the Event ID 1054 which
    states "Windows cannot obtain the Domain controller name
    for your computer network. (The specified domain either
    does not exist or could not be contacted). Group Policy
    processing aborted".
    I believe the error has to do we name resolution....we
    have DNS installed and it appears to be working fine
    (based on the Event Viewer) although when I run
    Netdiag.exe I get a warning "Failed to query SPN
    registration on DC". Microsoft says this warning is not
    necessarily a cause for concern.I tried installed WINS
    and it makes no difference. Any suggestions would be
    appreciated.
     
    SP, Jul 14, 2004
    #1
    1. Advertisements

  2. What DNS server do the AD clients point to?


    DDS WW 2k MVP MCSE
     
    Danny Sanders, Jul 14, 2004
    #2
    1. Advertisements

  3. All client machines must have the AD DNS Server in their network settings
    (either static or by DHCP).

    How to: Configure DNS for Internet Access In Windows 2000
    http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

    323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
    http://support.microsoft.com/default.aspx?scid=kb;en-us;323380

    825036 - Best practices for DNS client settings in Windows 2000 Server and
    in Windows Server 2003
    http://support.microsoft.com/default.aspx?scid=kb;en-us;825036
     
    Phillip Windell, Jul 14, 2004
    #3
  4. SP

    SP Guest

    Our AD Clients use DHCP and use our own DNS server to
    resolve IP addresses. The DNS server is the same one we
    have been using for years and after the upgrade we made
    the W2K server a DC.
     
    SP, Jul 14, 2004
    #4
  5. SP

    SP Guest

    Our AD clients use DHCP to obtain their network
    settings. We use our own DNS server which was upgraded
    to a W2K server DC after our upgrade to 2003.
     
    SP, Jul 14, 2004
    #5
  6. Danny Sanders, Jul 14, 2004
    #6
  7. SP

    Guest Guest

    Hello,

    I have installed both DCDiag & NetDiag on the first DNS
    server and ran the following;
    1.DCdiag /test:registerindns /dnsdomain:example.microsoft.
    com
    2.Netdiag /test:dsgetdc /d:c.b.a.com /v
    3.Netdiag.
    All tests Passed except when I ran Netdiag the "WARNING
    Failed to query SPN registration on DC" appeared.

    One thing I would like to add is that we still see our
    Netbois name XX-XXXXXXX Domain name instead of
    A.B.C.on.ca when we log on to the network. Is this
    correct?
     
    Guest, Jul 14, 2004
    #7
  8. Danny Sanders, Jul 14, 2004
    #8
  9. SP

    SP Guest

    Hello Dan,

    I had a look at the knowledge base however our Server is
    running with SP4 and I cannot find a hotfix for the
    problem that we are encountering. Any other suggestion?
    I appreciate your feedback.
     
    SP, Jul 15, 2004
    #9
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.