Re: child domain did not register with parent - help

Hi Todd
I tried everything and it didn't work so I reinstalled w2k3. Drastic I know
but it was a brand new box so I started from scratch.

Here's where I am now.
I have a parent domain
child domain A
child domain B

I reinstalled on child domain B
I joined the parent as a child. That was successful.

I went to parent and zone was showing BUT there was a missing entry,
DNSDomainZone is missing. I'm sure that's part of my problem.

For child B the following information is in DNS:
msdcs
sites
tcp
udp
name server entry

I went to child A and parent AD sites and serves with the following result:
I go to child B
right click, go to NTDS settings, the domain is registered but the server
name is incorrect??? Weird and getting weirder....It shows the name of the
old zone that also didn't work. Should I delete this one?

I changed the name of the servers that child B should replicate with. Child
A was showing so I added Parent. It still didn't work.


Also, when I click in right pane, click on parent and click replicate now
I receive the following message:
RPC server is unavailable, possibly a DNS lookup error
I try to browse the network. I see the child B domain but I can't see a
list of servers. The error reads that the list of domain controllers is
unavailable.

Child A can replicate to Child B.
Child B cannot replicate to Child A or parent.
Parent cannot replicate to Child B, only Child A

I'm getting KCC errors due to replication.

Any help would be greatly appreciated.
--
P Cully


"Todd J Heron" wrote:

> Conduct the following 7-point check:
>
> 1) External DNS servers are configured under TCP/IP properties. Only use
> internal DNS servers when part of an Active Directory domain. AD Domain
> machines must never be pointed at an external (ISP) DNS server or even use
> an ISP DNS server as an "Alternate DNS server".
> 2) AD/DNS zone not configured to allow dynamic updates.
> 3) 'Register this connection's address" in DNS is not enabled under TCP/IP
> properties.
> 4) Not authenticated to the domain (due to DNS misconfiguration or DNS
> server problem)
> 5) Missing or incorrect "Primary DNS suffix" or "Connection-specific DNS
> suffix" of the domain to which the machine belongs. With a
> missing/incorrect DNS suffix a machine cannot find the correct zone to
> register in.
> 6) A Group Policy is forcing secure updates and the machine isn't a member
> of the domain..
> 7) DHCP client service not running. This is a requirement for DNS
> registration and DNS resolution even if the client is not actually using
> DHCP. See the below articles.
>
> No DNS Name Resolution If DHCP Client Service Is Not Running
> http://support.microsoft.com/default.aspx?scid=kb;en-us;268674
>
> Dynamic DNS Updates Do Not Work if the DHCP Client Service Stops
> http://support.microsoft.com/default.aspx?scid=kb;en-us;264539
>
> Note: DHCP can register the client in DNS, provided the DHCP server machine
> itself has the proper DNS servers set in it's TCP/IP properties.
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>
>
.

Relevant Pages

  • Re: set up first child DC in a remote site
    ... has not set its IP and DNS in the creation of ... delegation can the parent DC see the child DC-to-be? ... and child zone created as the Conditional forwarding configured pointing to ...
    (microsoft.public.windows.server.active_directory)
  • Re: set up first child DC in a remote site
    ... Since step 3 is done before installing the DNS on it, ... necessary to put the DNS server pointing to the parent domain. ... DC on the Child doamin and it's IP Address, at the moment that you create ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication Headache - Urgent please Assist!
    ... 1.Manually created a delegation for the child domain on our root server DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: set up first child DC in a remote site
    ... The reason I put step 3 in front of step 4 is that if the child DC-to-be has ... not set its IP and DNS in the creation of delegation ... can the parent DC see the child DC-to-be? ... Forwarding to point to the parent domain, point the server to itself under ...
    (microsoft.public.windows.server.active_directory)
  • Re: Misconfigured AD
    ... I have a Parent domain with 2 child domains and an exchange server ... I agree with Herb that it's more than likely a DNS misconfiguration. ...
    (microsoft.public.windows.server.active_directory)