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

From: Roger Abell (mvpNOSpam_at_asu.edu)
Date: 07/31/04 

Date: Sat, 31 Jul 2004 02:31:58 -0700

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
"Peter Afonin" <peter@gudzon.net> wrote in message
news:uIh2llndEHA.3148@TK2MSFTNGP10.phx.gbl...
> 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
>
> "Miha Pihler" <mihap-news@atlantis.si> wrote in message
> news:#zcvzQndEHA.2384@TK2MSFTNGP09.phx.gbl...
> > 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
> >
> > "Peter Afonin" <peter@gudzon.net> wrote in message
> > news:%23lnn4SmdEHA.4092@TK2MSFTNGP10.phx.gbl...
> > > 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
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: sys vol check
    ... instead of the local DNS server and two ISP DNS servers. ... I need to configure the DHCP to use all three internal DNS servers ... If DNS zones are AD Integrated are writtable. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Directory Service Event 1311
    ... The main issue was DNS. ... I had to point all DNS servers, ... port query tool to see what was being filtered. ... NLTEST is a support tool. ...
    (microsoft.public.windows.server.active_directory)
  • Re: sys vol check
    ... You've 3 DC DNS servers one in each Site with different subnets. ... You've A forward lookup Zone named CORP.DLECINC.COM and a reverse lookup ... The clients should use only their local DNSserver in ther NIC ...
    (microsoft.public.windows.server.active_directory)
  • Re: Win2k3 and Slow Logons
    ... > various DNS settings from the server and my router set up. ... for internal DNS servers, but it must NOT be listed on any ... >>>>bad world of the Internet. ...
    (microsoft.public.windows.server.dns)
  • Re: Prevent Caching of real world domain in W2K3 sp1 DNS.
    ... resolve anything usda.gov on either of my main DNS servers. ... and the cache is quite full. ...
    (microsoft.public.windows.server.dns)