Re: Domain controller not a global catalog, but is registered as i

Whoops, I understand the ou question you are actually referring to DNS.

The forestDnsZone and DomainDnsZone's are created when you create a new
forest in 2003 if you upgraded there is a good chance it doesn't exist.
This is a new partition that is shared specifically between 2003 dc's that
have dns on them. Windows 2000 dc's don't understand this partition and
can't read from it (Since they can't create it).

If this is an upgrade or 2000 AD I don't believe you have to worry, plus
there were no errors when you ran the netdiag and dcdiag diagnostics.


--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup

This posting is provided "AS IS" with no warranties, and confers no rights.

"CasinoSA" <CasinoSA@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:640CCD4F-5BDA-40D3-B9D6-A8E9BA088A6F@xxxxxxxxxxxxxxxx
Is it possible to have a functioning domain without the ForestDnsZones
orDomainDnsZones OUs? Is it possible to restore them if they are gone?
What
does this mean? These are errors I receive

Starting test: CutoffServers
* Configuration Topology Aliveness Check
* Analyzing the alive system replication topology for
DC=ForestDnsZones,DC=TMCasino,DC=local.
* Performing upstream (of target) analysis.
DsReplicaSyncAllW failed with error The naming context could not
be
found..
* Performing downstream (of target) analysis.
DsReplicaSyncAllW failed with error The naming context could not
be
found..
* Analyzing the alive system replication topology for
DC=DomainDnsZones,DC=TMCasino,DC=local.
* Performing upstream (of target) analysis.
DsReplicaSyncAllW failed with error The naming context could not
be
found..
* Performing downstream (of target) analysis.
DsReplicaSyncAllW failed with error The naming context could not
be
found..



"Paul Bergson" wrote:

This could be an OpenView issue.

Run diagnostics against your Active Directory domain.

If you don't have the tools installed, install them from your server
install
disk.
d:\support\tools\setup.exe

Run dcdiag and netdiag in verbose mode.
-> dcdiag /e /c /v /s:DC_Name /f:c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log

If you download a gui script I wrote it should be simple to set and run.
It
also has the option to run individual tests without having to learn all
the
switch options. The details will be output in notepad text files that
pop
up automagically.

The script is located in the download section on my website at
http://www.pbbergs.com

Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)

When complete search for fail, error and warning messages.


--
Paul Bergson MCT, MCSE, MCSA, Security+, CNE, CNA, CCA
http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup

This posting is provided "AS IS" with no warranties, and confers no
rights.

"CasinoSA" <CasinoSA@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2264C00A-2C2C-48D8-9ECF-B83AFB5CAB0D@xxxxxxxxxxxxxxxx
Using OpenView, we receive a message that says

"Domain controller dc1.domain.local is not a global catalog host, but
it
is
registered as one in DNS"

It should be a global catalog server. We have two domain controllers
and
both have the Global Catalog checkboxes checked under ADSS. What could
be
causing this message?






.

Relevant Pages

  • Re: Domain controller not a global catalog, but is registered as i
    ... Performing upstream analysis. ... DsReplicaSyncAllW failed with error The naming context could not ... Performing downstream (of target) analysis. ... It should be a global catalog server. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Domain controller not a global catalog, but is registered as i
    ... Performing upstream analysis. ... DsReplicaSyncAllW failed with error The naming context could not be ... Performing downstream (of target) analysis. ... "Domain controller dc1.domain.local is not a global catalog host, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Adding target domain on source domains workstation for migration
    ... we can create LMHOSTS files to point the clients to the target ... How to Write an LMHOSTS File for Domain Validation and Other Name ... 228803 DHCP Dynamic Updates with DNS ... 323360 How to install and configure a DHCP Server in an Active Directory ...
    (microsoft.public.windows.server.migration)
  • [EXPL] Kaminsky DNS Cache Poisoning Flaw Exploit for Domains
    ... Kaminsky DNS Cache Poisoning Flaw Exploit for Domains ... allow the insertion of malicious DNS records into the cache of the target ... This exploit caches a single malicious nameserver entry into ... target server including an answer for the query, ...
    (Securiteam)
  • Re: Forest Migration DNS configuration?
    ... I have a small forest migration, my windows 2000 domain in the source ... I have configured the trusts but having attempted a number of DNS ... configurations have not been able to get intraforest name resolution ... Essentially I have configured zone transfers from the target domain ...
    (microsoft.public.windows.server.dns)