New 2000 Server DC

I have just installed a new DC as a Child of a parent domain and I am
running into communication problems. This new server has AD setup and DNS
as well loaded. This server is suppose to handle dns for this child domain,
but for some reason it is not communicating back with the root DC which is a
2003 server and handles the GC. I ran a netdiag on this child DC and got
this:

Computer Name: HT_DC
DNS Host Name: ht_dc.ht.hrm.lan
System info : Windows 2000 Server (Build 2195)
Processor : x86 Family 6 Model 8 Stepping 1, GenuineIntel
List of installed hotfixes :
KB820888
KB822831
KB823182
KB823559
KB824105
KB824141
KB824146
KB825119
KB826232
KB828028
KB828035
KB828749
KB829558
Q147222


Netcard queries test . . . . . . . : Passed



Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed

Host Name. . . . . . . . . : ht_dc.ht.hrm.lan
IP Address . . . . . . . . : 10.0.3.3
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 10.0.3.1
Dns Servers. . . . . . . . : 10.0.3.3
192.168.2.1
192.168.1.6


AutoConfiguration results. . . . . . : Passed

Default gateway test . . . : Passed

NetBT name test. . . . . . : Passed
No remote names have been found.

WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{AE31EEF2-629D-4DA8-B8B3-C2C881E7E2FD}
1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Failed
[WARNING] The DNS host name 'ht_dc.ht.hrm.lan' valid only on Windows
2000 DN
S Servers. [DNS_ERROR_NON_RFC_NAME]
[FATAL] Failed to fix: DC DNS entry
_ldap._tcp.0a2c8c57-0fd5-44e7-81ba-cb625
0c4d8d7.domains._msdcs.hrm.lan. re-registeration on DNS server '10.0.3.3'
failed
..
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Failed to fix: DC DNS entry
2682b51b-d6ef-4caf-bb69-173bf336f6c9._ms
dcs.hrm.lan. re-registeration on DNS server '10.0.3.3' failed.
DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
[FATAL] Fix Failed: netdiag failed to re-register missing DNS entries
for th
is DC on DNS server '10.0.3.3'.
[FATAL] No DNS servers have the DNS records for this DC registered.


Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{AE31EEF2-629D-4DA8-B8B3-C2C881E7E2FD}
The redir is bound to 1 NetBt transport.

List of NetBt transports currently bound to the browser
NetBT_Tcpip_{AE31EEF2-629D-4DA8-B8B3-C2C881E7E2FD}
The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Failed
[FATAL] Cannot find DC in domain 'HT'. [ERROR_NO_SUCH_DOMAIN]


DC list test . . . . . . . . . . . : Failed
'HT': Cannot find DC to get DC list from [test skipped].


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Skipped
'HT': Cannot find DC to get DC list from [test skipped].


LDAP test. . . . . . . . . . . . . : Failed
Cannot find DC to run LDAP tests on. The error occurred was: The
specified d
omain either does not exist or could not be contacted.



Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Passed
IPSec policy service is active, but no policy is assigned.


The command completed successfully

I am also getting event errors sayiong it can't contact the global catalog.
In my dns settings I have this DC pointing to itself as the primary DNS
server and then the root server which is also a dns server as the secondary.
I can ping the root DC from this child DC.

Hope someone can give me an answer.

Thanks!
--
Scott Micale
330-877-3631




Scott Micale

In item <uKynx2J$(E-Mail Removed)>,
Scott Micale says...

> I have just installed a new DC as a Child of a parent domain and I am
> running into communication problems. This new server has AD setup and DNS
> as well loaded. This server is suppose to handle dns for this child domain,
> but for some reason it is not communicating back with the root DC which is a
> 2003 server and handles the GC. I ran a netdiag on this child DC and got
> this:
>
> Computer Name: HT_DC
> DNS Host Name: ht_dc.ht.hrm.lan
> System info : Windows 2000 Server (Build 2195)
> Processor : x86 Family 6 Model 8 Stepping 1, GenuineIntel
> List of installed hotfixes :
> KB820888
> KB822831
> KB823182
> KB823559
> KB824105
> KB824141
> KB824146
> KB825119
> KB826232
> KB828028
> KB828035
> KB828749
> KB829558
> Q147222
>
>
> Netcard queries test . . . . . . . : Passed
>
>
>
> Per interface results:
>
> Adapter : Local Area Connection
>
> Netcard queries test . . . : Passed
>
> Host Name. . . . . . . . . : ht_dc.ht.hrm.lan
> IP Address . . . . . . . . : 10.0.3.3
> Subnet Mask. . . . . . . . : 255.255.255.0
> Default Gateway. . . . . . : 10.0.3.1
> Dns Servers. . . . . . . . : 10.0.3.3
> 192.168.2.1
> 192.168.1.6
>
>
> AutoConfiguration results. . . . . . : Passed
>
> Default gateway test . . . : Passed
>
> NetBT name test. . . . . . : Passed
> No remote names have been found.
>
> WINS service test. . . . . : Skipped
> There are no WINS servers configured for this interface.
>
>
> Global results:
>
>
> Domain membership test . . . . . . : Passed
>
>
> NetBT transports test. . . . . . . : Passed
> List of NetBt transports currently configured:
> NetBT_Tcpip_{AE31EEF2-629D-4DA8-B8B3-C2C881E7E2FD}
> 1 NetBt transport currently configured.
>
>
> Autonet address test . . . . . . . : Passed
>
>
> IP loopback ping test. . . . . . . : Passed
>
>
> Default gateway test . . . . . . . : Passed
>
>
> NetBT name test. . . . . . . . . . : Passed
>
>
> Winsock test . . . . . . . . . . . : Passed
>
>
> DNS test . . . . . . . . . . . . . : Failed
> [WARNING] The DNS host name 'ht_dc.ht.hrm.lan' valid only on Windows
> 2000 DN
> S Servers. [DNS_ERROR_NON_RFC_NAME]
> [FATAL] Failed to fix: DC DNS entry
> _ldap._tcp.0a2c8c57-0fd5-44e7-81ba-cb625
> 0c4d8d7.domains._msdcs.hrm.lan. re-registeration on DNS server '10.0.3.3'
> failed
> .
> DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> [FATAL] Failed to fix: DC DNS entry
> 2682b51b-d6ef-4caf-bb69-173bf336f6c9._ms
> dcs.hrm.lan. re-registeration on DNS server '10.0.3.3' failed.
> DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> [FATAL] Fix Failed: netdiag failed to re-register missing DNS entries
> for th
> is DC on DNS server '10.0.3.3'.
> [FATAL] No DNS servers have the DNS records for this DC registered.
>
>
> Redir and Browser test . . . . . . : Passed
> List of NetBt transports currently bound to the Redir
> NetBT_Tcpip_{AE31EEF2-629D-4DA8-B8B3-C2C881E7E2FD}
> The redir is bound to 1 NetBt transport.
>
> List of NetBt transports currently bound to the browser
> NetBT_Tcpip_{AE31EEF2-629D-4DA8-B8B3-C2C881E7E2FD}
> The browser is bound to 1 NetBt transport.
>
>
> DC discovery test. . . . . . . . . : Failed
> [FATAL] Cannot find DC in domain 'HT'. [ERROR_NO_SUCH_DOMAIN]
>
>
> DC list test . . . . . . . . . . . : Failed
> 'HT': Cannot find DC to get DC list from [test skipped].
>
>
> Trust relationship test. . . . . . : Skipped
>
>
> Kerberos test. . . . . . . . . . . : Skipped
> 'HT': Cannot find DC to get DC list from [test skipped].
>
>
> LDAP test. . . . . . . . . . . . . : Failed
> Cannot find DC to run LDAP tests on. The error occurred was: The
> specified d
> omain either does not exist or could not be contacted.
>
>
>
> Bindings test. . . . . . . . . . . : Passed
>
>
> WAN configuration test . . . . . . : Skipped
> No active remote access connections.
>
>
> Modem diagnostics test . . . . . . : Passed
>
> IP Security test . . . . . . . . . : Passed
> IPSec policy service is active, but no policy is assigned.
>
>
> The command completed successfully
>
> I am also getting event errors sayiong it can't contact the global catalog.
> In my dns settings I have this DC pointing to itself as the primary DNS
> server and then the root server which is also a dns server as the secondary.
> I can ping the root DC from this child DC.
>
> Hope someone can give me an answer.
>
> Thanks!

This is a DNS specific issue. Post this to microsoft.public.windows.server.dns
and you will get an answer quickly.

--
Regards,

Michael Holzemer
No email replies please - reply in newsgroup

Learn script faster by searching here
http://www.microsoft.com/technet/tre...er/default.asp

You MUST be pointing to the DNS server hosting your AD namespace. Most
likely this will be the DNS server for the forest root.

You can delegate control of the zone to the local for the child domain if
you want.

"Michael Holzemer" <(E-Mail Removed)> wrote in message
news:esqdCoK$(E-Mail Removed)...
> In item <uKynx2J$(E-Mail Removed)>,
> Scott Micale says...
>
> > I have just installed a new DC as a Child of a parent domain and I am
> > running into communication problems. This new server has AD setup and
DNS
> > as well loaded. This server is suppose to handle dns for this child
domain,
> > but for some reason it is not communicating back with the root DC which
is a
> > 2003 server and handles the GC. I ran a netdiag on this child DC and
got
> > this:
> >
> > Computer Name: HT_DC
> > DNS Host Name: ht_dc.ht.hrm.lan
> > System info : Windows 2000 Server (Build 2195)
> > Processor : x86 Family 6 Model 8 Stepping 1, GenuineIntel
> > List of installed hotfixes :
> > KB820888
> > KB822831
> > KB823182
> > KB823559
> > KB824105
> > KB824141
> > KB824146
> > KB825119
> > KB826232
> > KB828028
> > KB828035
> > KB828749
> > KB829558
> > Q147222
> >
> >
> > Netcard queries test . . . . . . . : Passed
> >
> >
> >
> > Per interface results:
> >
> > Adapter : Local Area Connection
> >
> > Netcard queries test . . . : Passed
> >
> > Host Name. . . . . . . . . : ht_dc.ht.hrm.lan
> > IP Address . . . . . . . . : 10.0.3.3
> > Subnet Mask. . . . . . . . : 255.255.255.0
> > Default Gateway. . . . . . : 10.0.3.1
> > Dns Servers. . . . . . . . : 10.0.3.3
> > 192.168.2.1
> > 192.168.1.6
> >
> >
> > AutoConfiguration results. . . . . . : Passed
> >
> > Default gateway test . . . : Passed
> >
> > NetBT name test. . . . . . : Passed
> > No remote names have been found.
> >
> > WINS service test. . . . . : Skipped
> > There are no WINS servers configured for this interface.
> >
> >
> > Global results:
> >
> >
> > Domain membership test . . . . . . : Passed
> >
> >
> > NetBT transports test. . . . . . . : Passed
> > List of NetBt transports currently configured:
> > NetBT_Tcpip_{AE31EEF2-629D-4DA8-B8B3-C2C881E7E2FD}
> > 1 NetBt transport currently configured.
> >
> >
> > Autonet address test . . . . . . . : Passed
> >
> >
> > IP loopback ping test. . . . . . . : Passed
> >
> >
> > Default gateway test . . . . . . . : Passed
> >
> >
> > NetBT name test. . . . . . . . . . : Passed
> >
> >
> > Winsock test . . . . . . . . . . . : Passed
> >
> >
> > DNS test . . . . . . . . . . . . . : Failed
> > [WARNING] The DNS host name 'ht_dc.ht.hrm.lan' valid only on Windows
> > 2000 DN
> > S Servers. [DNS_ERROR_NON_RFC_NAME]
> > [FATAL] Failed to fix: DC DNS entry
> > _ldap._tcp.0a2c8c57-0fd5-44e7-81ba-cb625
> > 0c4d8d7.domains._msdcs.hrm.lan. re-registeration on DNS server
'10.0.3.3'
> > failed
> > .
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Failed to fix: DC DNS entry
> > 2682b51b-d6ef-4caf-bb69-173bf336f6c9._ms
> > dcs.hrm.lan. re-registeration on DNS server '10.0.3.3' failed.
> > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > [FATAL] Fix Failed: netdiag failed to re-register missing DNS
entries
> > for th
> > is DC on DNS server '10.0.3.3'.
> > [FATAL] No DNS servers have the DNS records for this DC registered.
> >
> >
> > Redir and Browser test . . . . . . : Passed
> > List of NetBt transports currently bound to the Redir
> > NetBT_Tcpip_{AE31EEF2-629D-4DA8-B8B3-C2C881E7E2FD}
> > The redir is bound to 1 NetBt transport.
> >
> > List of NetBt transports currently bound to the browser
> > NetBT_Tcpip_{AE31EEF2-629D-4DA8-B8B3-C2C881E7E2FD}
> > The browser is bound to 1 NetBt transport.
> >
> >
> > DC discovery test. . . . . . . . . : Failed
> > [FATAL] Cannot find DC in domain 'HT'. [ERROR_NO_SUCH_DOMAIN]
> >
> >
> > DC list test . . . . . . . . . . . : Failed
> > 'HT': Cannot find DC to get DC list from [test skipped].
> >
> >
> > Trust relationship test. . . . . . : Skipped
> >
> >
> > Kerberos test. . . . . . . . . . . : Skipped
> > 'HT': Cannot find DC to get DC list from [test skipped].
> >
> >
> > LDAP test. . . . . . . . . . . . . : Failed
> > Cannot find DC to run LDAP tests on. The error occurred was: The
> > specified d
> > omain either does not exist or could not be contacted.
> >
> >
> >
> > Bindings test. . . . . . . . . . . : Passed
> >
> >
> > WAN configuration test . . . . . . : Skipped
> > No active remote access connections.
> >
> >
> > Modem diagnostics test . . . . . . : Passed
> >
> > IP Security test . . . . . . . . . : Passed
> > IPSec policy service is active, but no policy is assigned.
> >
> >
> > The command completed successfully
> >
> > I am also getting event errors sayiong it can't contact the global
catalog.
> > In my dns settings I have this DC pointing to itself as the primary DNS
> > server and then the root server which is also a dns server as the
secondary.
> > I can ping the root DC from this child DC.
> >
> > Hope someone can give me an answer.
> >
> > Thanks!
>
> This is a DNS specific issue. Post this to
microsoft.public.windows.server.dns
> and you will get an answer quickly.
>
> --
> Regards,
>
> Michael Holzemer
> No email replies please - reply in newsgroup
>
> Learn script faster by searching here
>
http://www.microsoft.com/technet/tre...er/default.asp
>
>
>

So if I point to the root server as my primary then delegate control to the
child, can I then switch the primary dns server back to point to the child
dc? How do I do the delegation?

Thanks Ron!

"Rob Elder, MVP-Networking" <(E-Mail Removed)> wrote in message
news:eQz2z5L$(E-Mail Removed)...
> You MUST be pointing to the DNS server hosting your AD namespace. Most
> likely this will be the DNS server for the forest root.
>
> You can delegate control of the zone to the local for the child domain if
> you want.
>
> "Michael Holzemer" <(E-Mail Removed)> wrote in message
> news:esqdCoK$(E-Mail Removed)...
> > In item <uKynx2J$(E-Mail Removed)>,
> > Scott Micale says...
> >
> > > I have just installed a new DC as a Child of a parent domain and I am
> > > running into communication problems. This new server has AD setup and
> DNS
> > > as well loaded. This server is suppose to handle dns for this child
> domain,
> > > but for some reason it is not communicating back with the root DC
which
> is a
> > > 2003 server and handles the GC. I ran a netdiag on this child DC and
> got
> > > this:
> > >
> > > Computer Name: HT_DC
> > > DNS Host Name: ht_dc.ht.hrm.lan
> > > System info : Windows 2000 Server (Build 2195)
> > > Processor : x86 Family 6 Model 8 Stepping 1, GenuineIntel
> > > List of installed hotfixes :
> > > KB820888
> > > KB822831
> > > KB823182
> > > KB823559
> > > KB824105
> > > KB824141
> > > KB824146
> > > KB825119
> > > KB826232
> > > KB828028
> > > KB828035
> > > KB828749
> > > KB829558
> > > Q147222
> > >
> > >
> > > Netcard queries test . . . . . . . : Passed
> > >
> > >
> > >
> > > Per interface results:
> > >
> > > Adapter : Local Area Connection
> > >
> > > Netcard queries test . . . : Passed
> > >
> > > Host Name. . . . . . . . . : ht_dc.ht.hrm.lan
> > > IP Address . . . . . . . . : 10.0.3.3
> > > Subnet Mask. . . . . . . . : 255.255.255.0
> > > Default Gateway. . . . . . : 10.0.3.1
> > > Dns Servers. . . . . . . . : 10.0.3.3
> > > 192.168.2.1
> > > 192.168.1.6
> > >
> > >
> > > AutoConfiguration results. . . . . . : Passed
> > >
> > > Default gateway test . . . : Passed
> > >
> > > NetBT name test. . . . . . : Passed
> > > No remote names have been found.
> > >
> > > WINS service test. . . . . : Skipped
> > > There are no WINS servers configured for this interface.
> > >
> > >
> > > Global results:
> > >
> > >
> > > Domain membership test . . . . . . : Passed
> > >
> > >
> > > NetBT transports test. . . . . . . : Passed
> > > List of NetBt transports currently configured:
> > > NetBT_Tcpip_{AE31EEF2-629D-4DA8-B8B3-C2C881E7E2FD}
> > > 1 NetBt transport currently configured.
> > >
> > >
> > > Autonet address test . . . . . . . : Passed
> > >
> > >
> > > IP loopback ping test. . . . . . . : Passed
> > >
> > >
> > > Default gateway test . . . . . . . : Passed
> > >
> > >
> > > NetBT name test. . . . . . . . . . : Passed
> > >
> > >
> > > Winsock test . . . . . . . . . . . : Passed
> > >
> > >
> > > DNS test . . . . . . . . . . . . . : Failed
> > > [WARNING] The DNS host name 'ht_dc.ht.hrm.lan' valid only on
Windows
> > > 2000 DN
> > > S Servers. [DNS_ERROR_NON_RFC_NAME]
> > > [FATAL] Failed to fix: DC DNS entry
> > > _ldap._tcp.0a2c8c57-0fd5-44e7-81ba-cb625
> > > 0c4d8d7.domains._msdcs.hrm.lan. re-registeration on DNS server
> '10.0.3.3'
> > > failed
> > > .
> > > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > > [FATAL] Failed to fix: DC DNS entry
> > > 2682b51b-d6ef-4caf-bb69-173bf336f6c9._ms
> > > dcs.hrm.lan. re-registeration on DNS server '10.0.3.3' failed.
> > > DNS Error code: DNS_ERROR_RCODE_SERVER_FAILURE
> > > [FATAL] Fix Failed: netdiag failed to re-register missing DNS
> entries
> > > for th
> > > is DC on DNS server '10.0.3.3'.
> > > [FATAL] No DNS servers have the DNS records for this DC
registered.
> > >
> > >
> > > Redir and Browser test . . . . . . : Passed
> > > List of NetBt transports currently bound to the Redir
> > > NetBT_Tcpip_{AE31EEF2-629D-4DA8-B8B3-C2C881E7E2FD}
> > > The redir is bound to 1 NetBt transport.
> > >
> > > List of NetBt transports currently bound to the browser
> > > NetBT_Tcpip_{AE31EEF2-629D-4DA8-B8B3-C2C881E7E2FD}
> > > The browser is bound to 1 NetBt transport.
> > >
> > >
> > > DC discovery test. . . . . . . . . : Failed
> > > [FATAL] Cannot find DC in domain 'HT'. [ERROR_NO_SUCH_DOMAIN]
> > >
> > >
> > > DC list test . . . . . . . . . . . : Failed
> > > 'HT': Cannot find DC to get DC list from [test skipped].
> > >
> > >
> > > Trust relationship test. . . . . . : Skipped
> > >
> > >
> > > Kerberos test. . . . . . . . . . . : Skipped
> > > 'HT': Cannot find DC to get DC list from [test skipped].
> > >
> > >
> > > LDAP test. . . . . . . . . . . . . : Failed
> > > Cannot find DC to run LDAP tests on. The error occurred was: The
> > > specified d
> > > omain either does not exist or could not be contacted.
> > >
> > >
> > >
> > > Bindings test. . . . . . . . . . . : Passed
> > >
> > >
> > > WAN configuration test . . . . . . : Skipped
> > > No active remote access connections.
> > >
> > >
> > > Modem diagnostics test . . . . . . : Passed
> > >
> > > IP Security test . . . . . . . . . : Passed
> > > IPSec policy service is active, but no policy is assigned.
> > >
> > >
> > > The command completed successfully
> > >
> > > I am also getting event errors sayiong it can't contact the global
> catalog.
> > > In my dns settings I have this DC pointing to itself as the primary
DNS
> > > server and then the root server which is also a dns server as the
> secondary.
> > > I can ping the root DC from this child DC.
> > >
> > > Hope someone can give me an answer.
> > >
> > > Thanks!
> >
> > This is a DNS specific issue. Post this to
> microsoft.public.windows.server.dns
> > and you will get an answer quickly.
> >
> > --
> > Regards,
> >
> > Michael Holzemer
> > No email replies please - reply in newsgroup
> >
> > Learn script faster by searching here
> >
>
http://www.microsoft.com/technet/tre...hnet/scriptcen
ter/default.asp
> >
> >
> >
>
>