I have a standalone Win2K3 server that is used for running terminal services. For security and administration purposes, I thought it would be a good idea to install Active Directory since it wasn't done upon installation 12 moniths ago. I followed the instructions available here:
Here are the settings I used:
I created the forward lookup zone, tested it to see if the server registered, rebooted just to be sure, tested it again, then ran dcpromo. It ran fine all the way through, rebooted, and then sat on the dreaded "preparing network connections" for 10 minutes before allowing me to log on. I ran through the AD installation checklist and discovered that the DNS Server service was stuck on "starting". I can kill the process then try to start it again, but when I start it manually, the progress indicator gets to about halfway then virtually stops. I then get the error "1053: the service did not respond to the start or control request in a timely fashion" and the service status remains stuck on "starting". After several reboots and an uninstall and reinstall DNS without luck, I'm out of ideas. It doesn't seem anyone has documented this exact problem before.
What's more, is that the server can ping itself - and resolve it's own name. Ping companyfs1 comes back with a reply from 192.168.0.2 and gives the FQDN of companyfs1.company.local. How is this possible? I know it's only querying itself, but I thought that would still use DNS.
Anyway, I'm convinced I did nothing wrong throughout the process so surely it's not terminal. Is there any workaround or will I be forced to demote the server and remove AD? Oh - and I hope the existing user accounts are intact.