LDAP query to speficied LDAP server on TCP port 389 failed

Discussion in 'DNS Server' started by Shash, May 29, 2009.

  1. Shash

    Shash Guest

    when i try to check DC with dnslint . i am getting this error - but the
    server is up and working fine..

    please help

    C:\Documents and Settings\DA>dnslint /ad /s 10.232.211.11

    DNSLint will attempt to verify the
    DNS entries used in AD replication

    Using 127.0.0.1 for LDAP
    Starting with 10.234.212.193 for DNS

    This process may take several minutes to complete.........
    LDAP query to speficied LDAP server on TCP port 389 failed
    Server Down


    LDAP query to speficied LDAP server on TCP port 389 failed
    LDAP server specified appears to be down

    Specify a different LDAP server and run the command again
     
    Shash, May 29, 2009
    #1

    1. Advertisements

  2. Shash

    Ace Fekay [Microsoft Certified Trainer] Guest


    Remove the 127.0.0.1 address from the DNS server IP list in the NIC's IP properties, and try again. If there are any ISP addresses, they need to be removed as well.

    --
    Ace

    This posting is provided "AS-IS" with no warranties or guarantees and
    confers no rights.

    Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
    Microsoft Certified Trainer


    For urgent issues, you may want to contact Microsoft PSS directly. Please
    check http://support.microsoft.com for regional support phone numbers.

    "Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
    http://twitter.com/acefekay
     
    Ace Fekay [Microsoft Certified Trainer], May 29, 2009
    #2

    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads

  1. Can't configure tcp/ip printer port-Error loading the Tcp Mib Libr

  2. error-389

  3. Windows Firewall closes tcp port (i.e. port 21) after two minutes

  4. Netstat and Port 389 (mad.exe)

  5. port 389 on SBS 2003 ISA 2004

  6. #monitor incoming port 389 requests

  7. LDAP simple bind authentication using port 389

  8. question about port 389 in windows 2000 server

Loading...