Results 1 to 3 of 3

Thread: LDAP query to speficied LDAP server on TCP port 389 failed

  1. #1
    Shash Guest

    LDAP query to speficied LDAP server on TCP port 389 failed

    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
    MCSE

  2. #2
    Ace Fekay [Microsoft Certified Trainer] Guest

    Re: LDAP query to speficied LDAP server on TCP port 389 failed

    "Shash" <Shash@discussions.microsoft.com> wrote in message news:61D4A242-44BE-4171-82DF-DD4510EEB1F3@microsoft.com...
    > 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
    > MCSE



    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
    aceman@mvps.RemoveThisPart.org

    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



  3. #3
    Join Date
    Jul 2011
    Posts
    330

    Re: LDAP query to speficied LDAP server on TCP port 389 failed

    I found a article on Microsoft site based on LDAP Port Assignments in Exchange Server. It is bit related to the above topic and I hope this can put more light on the current issue. If you can find a proper way of assigning port to LDAP on Windows server then the error might not appear. There is some misconfiguration causing the server connectivity failure.

    http://support.microsoft.com/kb/224447

Similar Threads

  1. Problem in binding the user in LDAP using Spring LDAP
    By deepti.agrawal in forum Software Development
    Replies: 1
    Last Post: 25-04-2011, 03:26 AM
  2. LDAP Query AD
    By shivinder in forum Active Directory
    Replies: 4
    Last Post: 03-06-2010, 11:23 AM
  3. Replies: 1
    Last Post: 24-03-2010, 10:12 PM
  4. LDAP query
    By Palaksi in forum Active Directory
    Replies: 3
    Last Post: 11-12-2008, 02:09 AM
  5. LDAP query can it be done ?
    By zscw1 in forum Active Directory
    Replies: 3
    Last Post: 13-11-2008, 10:08 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,643,371,889.28756 seconds with 17 queries