Re: Problems with Domain Replication

From: Chriss3 (noSpamHere_at_chrisse.se)
Date: 04/23/04


Date: Fri, 23 Apr 2004 22:47:54 +0200

Another way to what Brain already have give you.

Install Windows Server Support Tools found at your Windows Server CD, Use
the command line tool nltest with the follow syntax.

nltest/ dsregdns

it will help you to ensure the domain controller is registered.

-- 
Regards
Christoffer Andersson
No email replies please - reply in the newsgroup
------------------------------------------------
http://www.chrisse.se - Active Directory Tips
"Brian Desmond [MVP]" <desmondb@payton.cps.k12.il.us> skrev i meddelandet
news:un35JCPKEHA.2880@TK2MSFTNGP10.phx.gbl...
> John-
>
> Have you restarted the new DC since this started occurring?
>
> Is the new DC pointing to the other one for DNS and vice versa? This is
> crucial.
>
> On the new one, open a command prompt, and do a net stop netlogon,
followed
> by a net start netlogon, and a ipconfig /registerdns. See if that
registers
> the records.
>
> -- 
> -- 
> Brian Desmond
> Windows Server MVP
> desmondb@payton.cps.k12.il.us
>
> http://www.briandesmond.com
>
>
> "John Lundrigan" <jonel@glenavon1.demon.co.uk> wrote in message
> news:jbfg80d50p9son8bpcvcusiglih6o7jirt@4ax.com...
> > I am experiencing a very strange problem. I have created a Windows
> > 2003 Active Directory domain. I then install a second domain
> > controller into the domain. The second domain controller is initially
> > installed as a Windows 2003 Member Server and it joins the domain with
> > no problem at all.
> >
> > When I promote the Member Server to a domain controller it goes
> > without a problem and copies the domain partition across. After some
> > time I noticed the objects created on the new domain controller were
> > not appearing on the original controller.
> >
> > I spent some time checking out DNS configuration but could not find
> > anything wrong. Both domains could resolve URL's to IP addresses.
> > Finally I thought I might remove AD from the new controller and try
> > again, but when I tried to do this the uninstall failed because of the
> > domain controller had a problem with DNS.
> >
> > I looked in the DNS cache and discovered that there were errors in
> > trying to find guid._msdcs.---.---. So I looked in the forward lookup
> > zone for the _msdcs subdomain, but the only computer that was
> > registered there was the original domain controller.
> >
> > Now, as far as I know, the behaviour of an installing domain
> > controller is to load specific entries into DNS so that all it's
> > services can be found by clients.
> >
> > I've never had any problems like this under Win2K. Can anybody help
> > please?
> >
> > Regards
> >
> > John L
>
>


Relevant Pages

  • Re: new domain setup
    ... DCs DNS servers. ... The only services that I usually allow to run on my DCs are DNS and DHCP... ... > Domain Controller for now until I can go get the other machines. ... Boot from CD and do base install. ...
    (microsoft.public.windows.server.setup)
  • Re: NT4 and W2K3 Questions
    ... the only in-place upgrade path is to install Windows Server 2003 on the ... This does not have to be your present PDC. ... An AD domain controller for the domain XYZ cannot be contacted, ...
    (microsoft.public.windows.server.general)
  • NT4Emulator Registry Key, Dos and Donts
    ... I upgraded an NT4.0 PDC to W2K3 and AD, which installed DNS as well. ... I now have a second server that I performed an in-place NT4.0 -> W2K3 ... cannot contact the DC to complete the install. ... asks wether I want to make this an Additional Domain Controller, ...
    (microsoft.public.windows.server.active_directory)
  • NT4Emulator Registry Key, Dos and Donts
    ... I upgraded an NT4.0 PDC to W2K3 and AD, which installed DNS as well. ... I now have a second server that I performed an in-place NT4.0 -> W2K3 ... cannot contact the DC to complete the install. ... asks wether I want to make this an Additional Domain Controller, ...
    (microsoft.public.windows.server.migration)
  • Re: user list / shares
    ... I assume you are using an Active Directory domain. ... You may have to install netdiag on your domain controller first. ... When all is done open up the dns ...
    (microsoft.public.win2000.networking)