Can't remove old DC

[Guest]

I had two Windows 2000 servers in my domain, dc1 & dc2. The first (dc1) is
running Exchange 2000, DNS & AD, the second (dc2) is a file & print server
running DNS & AD. I am trying to replace dc1 and have installed a new 2000
server running exchange 2000, DNS & AD. If I turn off the first server there
are severe delays in accessing netowrk files, if you can at all and I get DNS
errors in the event log on dc2 & dc3 event id 4004 "The DNS server was
unable to complete directory service enumeration of zone .. This DNS server
is configured to use information obtained from Active Directory for this zone
and is unable to load the zone without it. Check that the Active Directory
is functioning properly and repeat enumeration of the zone. The event data
contains the error. ", "The DNS server was unable to complete directory
service enumeration of zone 1.1.192.in-addr.arpa. This DNS server is
configured to use information obtained from Active Directory for this zone
and is unable to load the zone without it. Check that the Active Directory
is functioning properly and repeat enumeration of the zone. The event data
contains the error. " "The DNS server was unable to complete directory
service enumeration of zone .. This DNS server is configured to use
information obtained from Active Directory for this zone and is unable to
load the zone without it. Check that the Active Directory is functioning
properly and repeat enumeration of the zone. The event data contains the
error. " E-mail is not accessable either. Help!!!

 

[Lawrence Tse]

It needs more information about your zone configuration before the
troubleshooting can hit the point. However, I will still try some
guessing...

From the symptoms seems like you are using Active Directory integrated zone
in your organization, right? In AD Intergrated zone, zone data is
replicated together with AD data and the first attemp should be at the time
when DC is first established. So, it should present with a basic set of DNS
data in DC2 & 3.

Network delay when accessing file after turning of DC1: seems like certain
portion of name resolution activity in your environment still depends on
DC1. Check your DNS/WINS (if you have) service setting on clients/DHCP
TCP/IP options to make sure IP or DC2 or DC3 are at the top of the list
instead of DC1.

DNS error: have you transfer your AD FSMO roles to another server before
shutting down DC1? other than transferring FSMO roles, you have to think
about Global Catalog Server as well. Have you ever define IP subnet in
Active Directory Sites and Services? And put appropreiate server into
appropreiate site? I think all these factor may introduce the error above.

If you need more specific trouble shooting, please kindly including more
specific information, include zone type, server physical location, server IP
(can be fake, but should show subnet dependency), FSMO and GC ownership,
client DHCP, DNS and WINS setting, etc.

Regards,

Lawrence Tse