DC of the Parent Domain can't Ping the hostname of the DC Child Do



Hi there,

Here's the situation with what I have:

1and only AD DC, Windows 2003 Standard R1, hostname "host1 - for sake of
argument" also acting as File Server in head office with all HO users and
branch users authenticating from it.

I added a child domain to it, hostname "host2" and It is Windows 2003
Standard R2. Both servers are communicating through VPN and all ports and
service are open.

I had to run "adprep /forestprep" command on the Parent domain(host1 - the
one with R1) from CD 2 of the Windows 2003 Server R2. This need to be done
as per Microsoft so current R1 server could communicate with R2 windows
during AD wizard.

Reboot both servers, and I'm able to ping from the Child to the Parent with
its hostname, "host1", but not the other way around. However, I could ping
host2's FQDN no problem; "host2.city2.ParentDomain.com"

The Parent, host1, knows about the child domain and its DC in the DNS
service. But I can't ping its hostname nor PCs on the Child domain. Please
help.

This is what I found on the Event Viewer on the Child Domain:

Event Viewer from the Child Domain:



The dynamic registration of the DNS record
'_ldap._tcp.25c022b9-78fc-4ee2-ae4f-943bc9fe10eb.domains._msdcs.auroraimporting.com.
600 IN SRV 0 100 389 host2.city2.ParentDomain.com.' failed on the following
DNS server:



DNS server IP address: 10.10.1.10

Returned Response Code (RCODE): 5

Returned Status Code: 9017

For computers and users to locate this domain controller, this record must
be registered in DNS.

USER ACTION

Determine what might have caused this failure, resolve the problem, and
initiate registration of the DNS records by the domain controller. To
determine what might have caused this failure, run DCDiag.exe. You can find
this program on the Windows Server 2003 installation CD in
Support\Tools\support.cab. To learn more about DCDiag.exe, see Help and
Support Center. To initiate registration of the DNS records by this domain
controller, run 'nltest.exe /dsregdns' from the command prompt on the domain
controller or restart Net Logon service. Nltest.exe is available in the
Microsoft Windows Server Resource Kit CD.

I will test the User Action and search the Status Code tomorrow.

Thank you for your help in advance.

.



Relevant Pages

  • Re: Domain Controllers Cant reach Default Gateway...
    ... Making the ISA a domain controller would ... DNS it was missing the CNAME entry with the GUID for the other ... DNS server doesn't support this feature. ... The problem is my XP Pro laptop. ...
    (microsoft.public.win2000.active_directory)
  • Re: Domain Controllers Cant reach Default Gateway...
    ... Making the ISA a domain controller would ... area of DNS it was missing the CNAME entry with the GUID ... DNS server doesn't support this feature. ... The problem is my XP Pro laptop. ...
    (microsoft.public.win2000.active_directory)
  • Re: Domain Controllers Cant reach Default Gateway...
    ... Making the ISA a domain controller would ... one of the domain controllers the active directory DNS zone ... DNS server doesn't support this feature. ... The problem is my XP Pro laptop. ...
    (microsoft.public.win2000.active_directory)
  • Re: Domain Controllers Cant reach Default Gateway...
    ... Making the ISA a domain controller would ... one of the domain controllers the active directory DNS zone ... DNS server doesn't support this feature. ... The problem is my XP Pro laptop. ...
    (microsoft.public.win2000.active_directory)
  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)

Loading