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

"Shash" <> wrote in message news:61D4A242-44BE-4171-82DF-...
> 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


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