The specified domain either does not exist or could not be contacted

Discussion in 'Server Security' started by Peter Afonin, Jul 30, 2004.

  1. Peter Afonin

    Peter Afonin Guest

    Hello,

    We have a Windows Server 2003 domain controller and Win2000 workstations.
    This problem occurs on only one computer, which I set up exactly the same
    way as any other that don't have this problem.

    When I go to the Computer Management and try to add any user from our domain
    to the Administrators (or any) group, I get this error:

    "The specified domain either does not exist or could not be contacted"

    Other than that there are no other issues: this computer is a part of the
    domain, connected to the network etc.

    I saw a few articles about this error message, but none of them apply to my
    situation.

    What could be a problem?

    I would appreciate your help.

    Thank you,
     
    Peter Afonin, Jul 30, 2004
    #1
    1. Advertisements

  2. Peter Afonin

    Miha Pihler Guest

    Hi Peter,

    I would check DNS settings. DNS entry should be IP of active directory
    server or DNS that knows something abut your internal domain (active
    directory) DNS.

    Try to ping DNS server and try to resolve e.g.

    nslookup DC_name

    where DC_name is a name of domain controller.

    Last thing that I would try is remove workstation from domain, restart it
    and then join it back to domain. (Before you disjoin workstation from
    domain, make sure you know local administrator password!)

    Mike
     
    Miha Pihler, Jul 30, 2004
    #2
    1. Advertisements

  3. Peter Afonin

    Peter Afonin Guest

    Thank you, Mike.

    I have no problem resolving DNS. I will try to disjoin the domain and join
    it again - you're correct, sometimes this fixes many problems.

    Peter

     
    Peter Afonin, Jul 30, 2004
    #3
  4. Peter Afonin

    Roger Abell Guest

    Umm. There is an intermediate.
    If you establish the machine is configured to use only
    the DNS servers intended for support of your AD, then
    it is possible that the DNS zones are not healthy.
    You can run the optional netdiag utility, from the support
    tools, to determine if DNS is OK. Just use it on each DC
    and see if it likes what it examines.

    --
    Roger Abell
    Microsoft MVP (Windows Server System: Security)
    MCSE (W2k3,W2k,Nt4) MCDBA
     
    Roger Abell, Jul 31, 2004
    #4
    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.