Paul,
It *could* be a DNS issue ( as you well know it can almost always be a DNS
issue! ) but I would be more inclined to think that it has something to do
with a Global Catalog.
However, the original poster did not really get into any sort of detail. I
am going to ass/u/me that he/she set up each of the seven Sites correctly in
the Active Directory Sites and Services ( create the six Sites - as the
first one is there for you already - and then create the existing Subnets
and then associate each Subnet with the appropriate Site ) and that all of
the clients are authenticating against the local DC ( not really part of
this issue - just a general statement ) and that there are neither any
IntraSite nor any InterSite replication issues. Furthermore, I would assume
that the only GC is available at all times. By adding a GC in each Site you
have the redundancy that is so crucial as well as the other things that are
associated with the GC.
However, since the poster did not tell us what the error is you could very
well be onto something, Paul.
I would make sure that I rebooted each DC after making it a Global Catalog
Server. I would suggest that the op install the set up Sites in the ADSS
MMC ( if not already done ), create a Reverse Lookup Zone in DNS, install
the Support Tools on all of his\her WIN2000 Servers ( in whatever capacity
they are ) and run both dcdiag /c /v on all of the Domain Controllers and
netdiag /v on all Servers. I would also run repadmin /showreps and repadmin
/showconn to make sure that everything is where it is supposed to be.
And let's not forget to check in the ESM to make sure that all DCs/GCs show
up. I hope that the original poster installed the Exchange Server Manager
( via the Custom Install ) on all of the remote DCs as well as then
installing the Exchange Service Pack on them. That would make things
easier.
HTH,
Cary
