Re: DC cannot see AD
- From: "elwappo" <elwappo@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 2 May 2005 16:22:01 -0700
Here's a pointer that DNS may be the issue:
http://support.microsoft.com/default.aspx?kbid=325322
How about changing the affected DC to point to the first DC that popped up
in the domain? Or whichever is the SOA for the domain .. or equivilant.
"Chriss3 [MVP]" wrote:
> Did you change the TCP/IP DNS Settings to point to the new DNS Server, or
> change the same options in the DHCP Scope if any?
>
> --
> Regards
> Christoffer Andersson
> Microsoft MVP - Directory Services
>
> No email replies please - reply in the newsgroup
> ------------------------------------------------
> http://www.chrisse.se - Active Directory Tips
>
> "Kahonu" <Kahonu@xxxxxxxxxxxxxxxxxxxxxxxxx> skrev i meddelandet
> news:7033C199-748B-4978-89C6-268B5DEA48E6@xxxxxxxxxxxxxxxx
> > Aloha kakou,
> > When trying to run "AD Users and Computers", I receive a
> > "Naming information cannot be located because:
> > The server is not operational.
> > Contact your sysadmin etc....."
> >
> > I suspect DNS. When all worked, I had a DC1, DC2 and DC3. DNS was running
> > on DC1 and DC2 with DNS being AD integrated. I need to take DC1 out of
> > service as it is having hardware issues. The plan was/is to remove DNS
> > from
> > DC1
> > and and add DNS to DC3. I did this and now I am getting the above message
> > on
> > DC2 and DC3. However, with the DNS Server service stopped on DC1, I can
> > still
> > access AD Users and Computers.
> >
> > Any help is appeciated.
> >
> > Mahalo,
> > Kahonu
> >
>
>
>
.
- Follow-Ups:
- Re: DC cannot see AD
- From: Kahonu
- Re: DC cannot see AD
- References:
- DC cannot see AD
- From: Kahonu
- Re: DC cannot see AD
- From: Chriss3 [MVP]
- DC cannot see AD
- Prev by Date: Re: Password Policy Issue
- Next by Date: Logon server in an enterprise enviroment
- Previous by thread: Re: DC cannot see AD
- Next by thread: Re: DC cannot see AD
- Index(es):
Relevant Pages
|
Loading