I've changed my Windows 2000 (advanced) server to a domain controller. It also serves as a DNS server and an IIS server.
It has been working as a DNS and IIS server fine for months. When I used the dcpromo to create the domain server I did all my checks and adjustments and the DNS portion as far as I can tell works just fine. I should mention, this server is not serving an enterprise, just me and my one other computer so there is no danger in overloading by have ISS DNS and AD on the same machine.
I then went to the security options and set up the security in accordance with this article (just to have a starting point since I am a newbie): http://www.securityfocus.com/infocus/1297
When I logged off of my client computer I could not log back onto the domain. I can log onto the computer locally.
The error message I get is the following: "windows cannot connect to the domain, either because domain controller is down or otherwise unavailable, or because your computer account was not found."
The steps I have taken so far to track this down are:
1. While logged onto the workstation locally, I changed the workstation name from capio4 to ws1. I saw it update in the AD so I know they are talking.
2. Checked the computer and my login are in the AD -- they have to be as I had been logging in previously but I checked anyway.
3. Set all the security back to "undefined" as it was before I applied the security template.
4. executed the following commands:
secedit ws1 /ENFORCE
secedit firstname.lastname@example.org /ENFORCE
secedit reg /ENFORCE
...and I still get the same error message.
My domain is capio.net. I've heard that something like capio.local would perhaps be better but I have the DNS lookup in my client going straight to my DNS server and then my DNS server forwards to my Internet Gateway and as far as I can tell it's fine that way since there has been no problems in the past with it that way.
Any help at this point greatly appreciated as I am all out of ideas.