Ldap will not connect to domain controller

[Aaron]

I cannot connect to my domain controller at work with
Ldap, and am therefore unable to login. Every one else is
able to login but me... Any ideas?

 

[David Jones]

Has this ever worked?
Can you please describe exactly what you do, and exactly
what happens (including error messages)?
Are there any errors in the event log?

 

[aaron]

Using the ldp.exe utility out of XP tools. I used to be
able to use the network fine, now I cannot browse to any
other computers, or printers. The error that ldp.exe
gives is : Error <0x51>: Fail to connect to 192.168.64.50.
When I try to connect to the domain using
mycomputer>properties>computer name>network ID the error
message is:
A domain controller could mot be located.
Then I go to details and get:
The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)
Can you help?

 

[David Jones]

On the XP machine, check your DNS server (via
ipconfig /all from a command prompt if it gets it
automatically). Is this your internal DNS server that is
part of the domain? Or is it your ISP's/router's DNS
server?

 

[aaron]

ISP's DNS server. Should I need DNS to log into an NT4
domain? Failed to mention that in previous message.

 

[David Jones]

Well, the error you have is that there was no DNS record
for the domain in question, which makes sense since How
do you resolve names on your network?
How many DC's are in your NT 4 domain - just the PDC or
do you have BDC's also?

What machine is 192.168.64.50 that you're trying to
connect to? Has it always been the same IP
address/machine that you've tried to connect to?

 

[David Jones]

Ok, this brings up additional questions. Step back a
minute.
You /do/ use DNS for name resolution internally?
If you're using DNS for name resoulution internally, you
MUST use the internal DNS server, and NOT the ISP's DNS
server. That will cause all this to happen, without a
doubt.

Take your LDAP utility out of the equation for now. What
are you trying to do, and what happens when you try to do
it? Are you having problems logging into the domain and
finding resources? Are there any errors in the event log?

I'm not convinced yet that resetting TCP/IP or
reinstalling is needed - do you have any idea if network
settings changed either on your machine or on the DC
since this last worked?