Domain Controller Server Not Operational

The server is not operational.

Domain controller server not operational. Naming information cannot be located for the following reason. Make the notification server a member server of your domain. This error has been seen in the windows server.

The server is not operational. Make sure the domain controller is listed in a dns zone that the notification server can resolve. The error stops you from accessing that particular service or setting.

Microsoft introduced knowledgebase article 2738697 with the title the server is not operational domain controller configuration error when you configure a server by using server manager. If it is not the command did not work. If the ntlm authentication has been disabled whether it is domain or domain controller then most likely this.

Alternatively they could ve named this knowledgebase article why you need to domain join proposed replica domain controllers first in active directory in windows server 2012. If you are typing to connect to a domain controller running windows 2000 verify that windows 2000 sp3 or later is installed on the dc or use the windows 2000 administration tools. Use the netdom tool from the windows 2000 server support tools or from the windows server 2003 support tools to reset the domain controller s machine account password.

If you are trying to access services or performing any operation then you get this error. The issue has been faced by many users all over the world. The server is not operational is a windows server error.

For the domain contoso where the affected domain controller is dc1 and a working domain controller is. For more information about connecting to dcs running windows 2000 see help and support the dns event viewer always. However when i first set this up and was having this problem i actually did not have the domain controller in the ldap string and some of the post i read said that they fixed this problem by specifying a specific one.