Archived from groups: microsoft.public.win2000.active_directory (
More info?)
"davisr65" <davisr65@discussions.microsoft.com> wrote in message
news:FF2CFCA2-8F5D-4BE3-B9D1-80E919A4E0E5@microsoft.com...
> Herb, Today I lost all NTFS permissions on my SAN drive and had to run
chkdsk
> /f which did restore the data, but....shares had to be recreated
manually...
> since then, the GC went down... on this server.., so i reset another
domain
> controller to takeover as the GC... My question to you ......There can be
> more than one Global catalog in a windows 2000 domain?
Yes. In small forests (all those with one domain) all DCs should usually
be GCs.
> ......it thought that
> only windows 2003 domain can have multiple GC's is this true let me
> know...Please let me know
No, it is incorrect. You may have as many GCs are you wish.
The only caveats are that you should not use excessive GCs in a multiple
Domain Forest when the domains are LARGE, and you should not have
the Infrastructure master be a GC unless ALL DCs in that domain are GCs.
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
>
> thank you all for your responses...
>
> "Herb Martin" wrote:
>
> > "davisr65" <davisr65@discussions.microsoft.com> wrote in message
> > news:8942D7B2-FACA-4078-8DC0-CC288ED1D24F@microsoft.com...
> > > Why is it when my 2 AD Server domain when my main server goes down
(the
> > first
> > > one added to the domain), nobody and log in?.....I thought the second
> > domain
> > > controller was the peer..... and I have integrated DNS running... do
i
> > have
> > > something configured wrong?
> >
> > Usually it is one of these: The only GCC is going down in Native Mode
OR
> > you have DNS issues.
> >
> > With a single domain forest you should make all DCs into GCs.
> >
> > Then double (triple) check your DNS. The vast majority of such problems
> > are really DNS issues.
> >
> > DNS for AD
> > 1) Dynamic for the zone supporting AD
> > 2) All internal DNS clients NIC\IP properties must specify SOLELY
> > that internal, dynamic DNS server (set.)
> > 3) DCs and even DNS servers are DNS clients too -- see #2
> > 4) If you have more than one Domain, every DNS server must
> > be able to resolve ALL domains (either directly or
indirectly)
> >
> > netdiag /fix
> >
> > ....or maybe:
> >
> > dcdiag /fix
> >
> > (Win2003 can do this from Support tools):
> > nltest /dsregdns /server
C-ServerNameGoesHere
> > http://support.microsoft.com/kb/q260371/
> >
> > Ensure that DNS zones/domains are fully replicated to all DNS
> > servers for that (internal) zone/domain.
> >
> > Also useful may be running DCDiag on each DC, sending the
> > output to a text file, and searching for FAIL, ERROR, WARN.
> >
> > Single Label domain zone names are a problem Google:
> > [ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
> >
> > --
> > Herb Martin, MCSE, MVP
> > Accelerated MCSE
> >
http://www.LearnQuick.Com
> > [phone number on web site]
> >
> >
> >