Discussion Locked

AD Domain Controller reboots on its own.

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Has anybody ever encountered a situation where a Domain Controller, in Active Directory, reboots itself automatically when trying view the user object database, in Active Directory, from a Windows NT domain controller. A two-way Trust Relationship is already established between the AD and the NT domain?

Situation:
We want to use the ADMT, therefore we needed to add the Domain Admins group from the NT domain and make it part of the local Administrators group in Active Directory and we also needed to add the Domain Admins group from Active Directory and make it part of the local Administrators group in the NT domain.

Inexplicable Reboot:
If we tried to add the Domain Admins group from Active Directory to the local Administrators group in the NT domain, with User Manger for Domains, FIRST, then we got an error message stating 'no server available to handle this RPC request' or 'RPC error'. Then one minute later the domain controller in Active Directory would display a warning message stating that the domain controller will reboot in 30 seconds please close applications, and then the domain controller rebooted.

Now, if we did the reverse the order and added the Domain Admins group from the NT domain to the local Administrators group in Active Directory FIRST and then add the Domain Admins group from the Active Directory to the local Administrators group in the NT domain SECOND, then the domain controller never rebooted.

Thanks in advance,
Anthony

1 reply

by joseph moore

RPC is crashing, which triggers the shutdown.
This Win2K machine IS patched for the DCOM/RPC vulnerability the Blaster worm triggers, is it?

This discussion is closed to new replies.