none
AD Error: Server Not Operational

    Question

  • Hello everybody,

     

    Pardon my noobishness but I'm just beginning to use Windows Server 2008 R2. After installing Active Directory (along with DNS services) it installs and works ok for a small while as in I am able to add users and such. Then afterwards when trying to access AD Users and Computers it comes up with this message:

    " Naming information cannot be located for the following reason: The server is not operational

    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. For more information about
    connecting to DCs running windows 2000, see help and support "

    The DNS event viewer always displays Event ID 4013, if that is a clue to what is going on. This happens on a fresh install, without much tinkering. Thank you for your time.

    Monday, August 30, 2010 6:13 PM

Answers

  •  

    Hi,

     

    Thank you for your post here.

     

    The obvious miss in the IP configuration is that  the gateway is configured as the DNS server on the DC. You may change it to 192.168.1.33 or 127.0.0.1 itself and check how it works.

     

    Tuesday, August 31, 2010 7:38 AM

All replies

  • Post output of IPCONFIG /ALL and DCDIAG /v /c from the DC

    hth
    Marcin

    Monday, August 30, 2010 6:24 PM
  • For IP Config /all :

     Volume in drive C has no label.
     Volume Serial Number is 26F9-429B

     Directory of c:\


    Windows IP Configuration

       Host Name . . . . . . . . . . . . : terminal
       Primary Dns Suffix  . . . . . . . : ****.com
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : Yes
       WINS Proxy Enabled. . . . . . . . : No
       DNS Suffix Search List. . . . . . : ****.com

    Ethernet adapter Local Area Connection 2:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #2
       Physical Address. . . . . . . . . : A4-BA-DB-45-0F-0F
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.1.33(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Default Gateway . . . . . . . . . : 192.168.1.254
       DNS Servers . . . . . . . . . . . : 192.168.1.254
       NetBIOS over Tcpip. . . . . . . . : Disabled

    Tunnel adapter isatap.{5F089151-5930-4F04-B61E-657F2978043F}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 9:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    for DCDIAG /v /c:


    Directory Server Diagnosis


    Performing initial setup:

       Trying to find home server...

       * Verifying that the local machine terminal, is a Directory Server.
       Home Server = terminal

       * Connecting to directory service on server terminal.

       Ldap search capabality attribute search failed on server terminal, return

       value = 81

     

    Monday, August 30, 2010 8:13 PM
  • This error indicates that AD DS is not responding to requests from the DNS Server service. Ensure that AD DS is functioning properly. Follow the below link



    If the above solution doesn't work you could alterntively try the solution for the ldap return value

    "Ldap search capabality attribute search failed on server terminal, return value = 81"


    Regards,
    Mani
    JiJi Technologies Team,
    Tuesday, August 31, 2010 6:27 AM
  •  

    Hi,

     

    Thank you for your post here.

     

    The obvious miss in the IP configuration is that  the gateway is configured as the DNS server on the DC. You may change it to 192.168.1.33 or 127.0.0.1 itself and check how it works.

     

    Tuesday, August 31, 2010 7:38 AM