- The fully qualified domain name of the machine does not match the domain name. That is, if you run IPCONFIG /ALL on the DC you will see a FQDN of server.company.com, and if you look at the domain name in Active Directory User and Computers you will see MYcompany.com. Thus, the machine is unable to find itself. Since this is a Windows 2000 domain (likely upgraded from a Windows NT 4.0 domain) you are in pretty bad shape. You might consider upgrading to Windows 2003 and then using the domain rename tool to rename the server's FQDN. Alternatively, if you have a backup of the NT 4.0 domain (if that is where this all originated) you can restore that, fix the FQDN and then upgrade to Windows 2000 again.
- You have a DNS issue. That's right, if the DNS is unable to locate all of the SRV (server records) you can get odd results. Run the DCDIAG.exe on the server and see what the results are.
- Someone has put a second domain with the same name on the same network. This will lead to all sorts of confusion for the client systems, and any system that is attempting to locate the server. DCDIAG.exe should offer a clue as to whether this is the case.
Dig Deeper on Windows administration tools
Related Q&A from Paul Hinsberg
Need to take an in-place upgraded PDC offline to rebuild it and use the second and third freshly-built 2003 DCs to handle services? Our expert ... Continue Reading
One admin wants to know if he can run DCPROMO on a Windows Server 2003 machine while the root domain is on Windows 2000. Continue Reading
A new admin's Active Directory is in utter chaos. Here's what our expert suggests. Continue Reading