Solved

Unable to re-add a domain contorller after running dcpromo /forceremoval

Posted on 2008-10-18
8
800 Views
Last Modified: 2013-12-05
I ma sitting at a client location that has two domain controlers. 1 Windows 2000 and 1 Windows 2003. The Windows 2003 controller had been unable to communicate long enough that it had past the tombstone period so I went ahead and removed the active directory however it was unsuccessful without using DCPromo /forceremoval. I forcably removed it and and went through on the Windows 2000 mahcine and cleaned up the metabase, dns, and ad.

Now I am trying to re-add the domain and it is continually failing giving me this error "The service did not respond to the start or control request in a timely matter" I get this error if I try to create the machine as a domain controller or as a computer on the domain.  Any ideas?
0
Comment
Question by:nlhess2003
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
8 Comments
 
LVL 63

Expert Comment

by:SysExpert
ID: 22750338
1) Are you sure you rpoperly removes everything, including the metadata ?

2) Double check AD and DNS

3) what shows up in the event logs of both  servers ?


I hope this helps !
0
 

Author Comment

by:nlhess2003
ID: 22750361
metadata looks clean as does AD and DNS.

No errors are reported in the logs on either machine.
0
 
LVL 42

Expert Comment

by:paulsolov
ID: 22751072
try this:

http://support.microsoft.com/kb/886695

Make sure that FSMO roles are on the DC.  There may be issues because the the AD was upgraded to 2003 and you're now working from a 2000 DC.  You may want to run adrep again
0
Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.

 

Author Comment

by:nlhess2003
ID: 22751140
All of the roles are on the Windows 2000 server. The Win 2000 server has been the primary domain controller all along. The Win 2003 server was just a backup DC that happened to not to synchromized for over a year locking it out. That is why I demoted it forcably. I will try the microsoft support article tomorrow.
0
 
LVL 31

Expert Comment

by:Henrik Johansson
ID: 22752578
Check the DNS settings on the joining computer and ensure that it's only pointing on a working DNS server authorative/aware of the AD DNS domain. As it has been a DC, it's propably pointing on itself for DNS resolution, but doesn't have the DNS service running/working correctly since the demote.
When promote is complete, configure both DCs to use the other DC/DNS as secondary DNS server to avoid problems.

Stop talking about primary/backup DC in AD environment. That is old NT4-stuff and doesn't exist in AD.
0
 

Author Comment

by:nlhess2003
ID: 22752686
The DNS Is configured correctly it is pointing to the DNS on the existing domain controller.
0
 
LVL 63

Expert Comment

by:SysExpert
ID: 22754487
Have you rebooted the win2k server after the cleanup ?

0
 

Accepted Solution

by:
nlhess2003 earned 0 total points
ID: 22772367
After trying everything under the sun we finally found a solution. Apperantly some of the networking services became corrupt after the force removal from the domain. We uninstalled Client for Microsoft Networking and reinstalled it through the properties on the Network Adapter on the . The reinstall was a little tricky it took 3 reboots of the server to get it to reappear in the networking options. Then the machines was able to be reconnected to the domain.
0

Featured Post

Why You Need a DevOps Toolchain

IT needs to deliver services with more agility and velocity. IT must roll out application features and innovations faster to keep up with customer demands, which is where a DevOps toolchain steps in. View the infographic to see why you need a DevOps toolchain.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article describes my battle tested process for setting up delegation. I use this process anywhere that I need to setup delegation. In the article I will show how it applies to Active Directory
This article shows the method of using the Resultant Set of Policy Tool to locate Group Policy that applies a particular setting.
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question