Event ID 5721

[SoonerIra]

Here is my config...

I have two Windows 2000 server active directory domain controllers. ALASKA is the PDC and WYOMING is the BDC.

WYOMING is the DNS, DHCP servers and is a secondary Exchange server with only a couple of mailboxes on it.

I restored the System State, SysVOL and the complete C: drive from backup using Backup exec. It came up with no errors. I had to install a RAID controller driver and after reboot I could not communicate with the domain. It sat on "Preparing network connections.." for about 10 minutes. Exchange server wouldn't start as well as most other servers on the machine.

I used the netdom command to reset the computer account and was then able to get it running.

All users on WYOMING can access their mailboxes and send/receive to anyone in the organization. All DNS request are resolved by the DNS server. The DHCP database got corrupted after the reboot and I had to recreate it and it is working fine now.

I added a new user today and it is not being replicated to WYOMING and the user is not able to log in to the domain. all other users are working fine.

I am getting the following errors in the System log:

Source: NETLOGON
Type: Error
Category: None
Event ID: 5721
Computer: WYOMING

The session setup to the Windows NT or Windows 2000 Domain Controller <Unknown> for the domain TULSA failed because the Domain Controller does not have an account for the computer WYOMING.

And in the Application Log:

Source: MSExchangeSA
Type: Error
Category: Monitoring
Event ID: 9098
Computer: WYOMING

Any help would be appreciated...

 

[aftertaf]

First off... there isnt such a thing as PDC and BDC in an active directory domain,
it is what they call a multimaster replication thingy.

How old was the backup you used to restore?

I used the netdom command to reset the computer account and was then able to get it running.

it seems to me that the two DCs no longer communicate or replicate since the account for wyoming has been changed...
There is probably a simpler and faster way to do this, but to be sure that everything is clean and functioning OK, what i'd do is this:

-Setup DNS on ALASKA - use a standard zone.
-Change DHCP to use ALASKA as DNS server.
-Get all DHCP clients + WYOMING to use ALASKA as their DNS (reboot clients or run ipconfig /release ipconfig /renew)
-Demote WYOMING to a member server
-if this doesn't work with a straightforward dcpromo, which is probably the case, check this page out.

http://support.microsoft.com/kb/332199/en-us

you'll need to do this on WYOMING then a metadata cleanup on ALASKA will probably be necessary.

Once it it done and WYOMING is no longer a DC:

configure your DNS zone to be active directory integrated (fault tolerance, for one !)
then dcpromo WYOMING to make it a DC again.
in your DHCP, specify both servers as DNS, in case one drops again...

Aftertaf (david)
MCSA 2003