I was at a client site this week and logged on to my machine using cached
credentials. I accessed the internet through the client's network. When I
returned to my office I was unable to logon to my machine, but I cannot
connect to any of the network servers. When we tried to reconnect me to the
network, we get an error that was looking for AD or an ldap, neither of which
we use. Is there a registry setting that may have gotten changed? Would
deleting the cached credentials fix this?

hi,
did you change your IP, dns, gateway? or if is a get by dhcp renew the ip or
reboot the machine.
--
Dragos CAMARA
MCSA Windows 2003 server


"digger665" wrote:

> I was at a client site this week and logged on to my machine using cached
> credentials. I accessed the internet through the client's network. When I
> returned to my office I was unable to logon to my machine, but I cannot
> connect to any of the network servers. When we tried to reconnect me to the
> network, we get an error that was looking for AD or an ldap, neither of which
> we use. Is there a registry setting that may have gotten changed? Would
> deleting the cached credentials fix this?

At the client site, we just plugged into their network and got an IP to get
out to the internet. At my office, I got a proper IP for our network and I
could get to the internet, but no internal servers. When we tried to
reconnect to the domain we got: The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.BIWER

We don't use Active Directory or ldap

"Dragos CAMARA" wrote:

> hi,
> did you change your IP, dns, gateway? or if is a get by dhcp renew the ip or
> reboot the machine.
> --
> Dragos CAMARA
> MCSA Windows 2003 server
>
>
> "digger665" wrote:
>
> > I was at a client site this week and logged on to my machine using cached
> > credentials. I accessed the internet through the client's network. When I
> > returned to my office I was unable to logon to my machine, but I cannot
> > connect to any of the network servers. When we tried to reconnect me to the
> > network, we get an error that was looking for AD or an ldap, neither of which
> > we use. Is there a registry setting that may have gotten changed? Would
> > deleting the cached credentials fix this?

In news:762551F6-66C7-4DCF-89FD-58DBE843D08E@microsoft.com,
digger665 <digger665@discussions.microsoft.com> typed:
> I was at a client site this week and logged on to my machine using
> cached credentials. I accessed the internet through the client's
> network. When I returned to my office I was unable to logon to my
> machine, but I cannot connect to any of the network servers. When we
> tried to reconnect me to the network, we get an error that was
> looking for AD or an ldap, neither of which we use. Is there a
> registry setting that may have gotten changed? Would deleting the
> cached credentials fix this?

Since you say you're using cached credentials, it *does* sound like you're
using AD (unless you're still on an NT domain). And if you're using AD, you
are in a sense using LDAP.

Otherwise, all you're doing
is logging into a local machine account, and there are no cached credentials
in that case.

What is the exact text of the error message, what do you see in the event
logs, and what is the exact config on your network in the office?

It is an NT Domain with NT domain controller.

This is the message:
The domain name BIWER might be a NetBIOS domain name. If this is the case,
verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the
following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location
(SRV) resource record used to locate a domain controller for domain BIWER:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.BIWER

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include delegation to its child
zone:

BIWER
.. (the root zone)

For information about correcting this problem, click Help.

"Lanwench [MVP - Exchange]" wrote:

> In news:762551F6-66C7-4DCF-89FD-58DBE843D08E@microsoft.com,
> digger665 <digger665@discussions.microsoft.com> typed:
> > I was at a client site this week and logged on to my machine using
> > cached credentials. I accessed the internet through the client's
> > network. When I returned to my office I was unable to logon to my
> > machine, but I cannot connect to any of the network servers. When we
> > tried to reconnect me to the network, we get an error that was
> > looking for AD or an ldap, neither of which we use. Is there a
> > registry setting that may have gotten changed? Would deleting the
> > cached credentials fix this?
>
> Since you say you're using cached credentials, it *does* sound like you're
> using AD (unless you're still on an NT domain). And if you're using AD, you
> are in a sense using LDAP.
>
> Otherwise, all you're doing
> is logging into a local machine account, and there are no cached credentials
> in that case.
>
> What is the exact text of the error message, what do you see in the event
> logs, and what is the exact config on your network in the office?
>
>
>
>

In news:5B6C2496-072B-4084-8B20-DBDB6BDA4729@microsoft.com,
digger665 <digger665@discussions.microsoft.com> typed:
> It is an NT Domain with NT domain controller.

Ouch...I hope you're thinking about upgrading/migrating. Of course, that
isn't too helpful now, so let's pretend I didn't write that.

>
> This is the message:
> The domain name BIWER

What is named BIWER?

> might be a NetBIOS domain name. If this is the
> case, verify that the domain name is properly registered with WINS.

Is it? Is *everything* registered properly in your WINS database?

>
> If you are certain that the name is not a NetBIOS domain name, then
> the following information can help you troubleshoot your DNS
> configuration.
>
> The following error occurred when DNS was queried for the service
> location (SRV) resource record used to locate a domain controller for
> domain BIWER:

Does your company network have an internal DNS server?

>
> The error was: "DNS name does not exist."
> (error code 0x0000232B RCODE_NAME_ERROR)
>
> The query was for the SRV record for _ldap._tcp.dc._msdcs.BIWER
>
> Common causes of this error include the following:
>
> - The DNS SRV record is not registered in DNS.
>
> - One or more of the following zones do not include delegation to its
> child zone:
>
> BIWER
> . (the root zone)
>
> For information about correcting this problem, click Help.

Presuming that you use DHCP on your company network, and the other network
used DHCP as well, make sure you get a new IP address (/release and /renew)
and also flush the DNS and NetBIOS cache (ipconfig /flushdns and nbtstat
/RR)

Since this issue isn't really client-related, you might post in a Windows
server or networking group if you can't get enough help in here.




>
> "Lanwench [MVP - Exchange]" wrote:
>
>> In news:762551F6-66C7-4DCF-89FD-58DBE843D08E@microsoft.com,
>> digger665 <digger665@discussions.microsoft.com> typed:
>>> I was at a client site this week and logged on to my machine using
>>> cached credentials. I accessed the internet through the client's
>>> network. When I returned to my office I was unable to logon to my
>>> machine, but I cannot connect to any of the network servers. When
>>> we tried to reconnect me to the network, we get an error that was
>>> looking for AD or an ldap, neither of which we use. Is there a
>>> registry setting that may have gotten changed? Would deleting the
>>> cached credentials fix this?
>>
>> Since you say you're using cached credentials, it *does* sound like
>> you're using AD (unless you're still on an NT domain). And if you're
>> using AD, you are in a sense using LDAP.
>>
>> Otherwise, all you're doing
>> is logging into a local machine account, and there are no cached
>> credentials in that case.
>>
>> What is the exact text of the error message, what do you see in the
>> event logs, and what is the exact config on your network in the
>> office?