Hi,

I joined one xp machine to the AD domain (2003). After rebooting the
machine, when i select the domain in the logon dialog box, it is showing
'connecting to the domain' message and it is still processing.

Any reason why it is not login to the domain but other system are able to
login.

Thanks,
Senthilkumaran B

This is almost always a DNS issue

Check that the computer has the Domain Controller listed at the primary
(first) DNS server.

Or, take a look at the network settings of the others that do work, and
follow.

In news:14295316-7DB4-446F-93A3-(E-Mail Removed),
Ian <(E-Mail Removed)> typed:
> This is almost always a DNS issue
>
> Check that the computer has the Domain Controller listed at the
> primary (first) DNS server.

To clarify, the internal DNS server (AD-integrated, most likely) should be
the *only* IP address listed for DNS. No public IPs should be in there.
>
> Or, take a look at the network settings of the others that do work,
> and follow.

Hi,

The exact message i got is "Creating the domain name list...Please wait."

The client is pointing to a BIND dns which forwards the queries to AD DNS
server.

thanks,
Senthilkumaran B

"Lanwench [MVP - Exchange]" wrote:

> In news:14295316-7DB4-446F-93A3-(E-Mail Removed),
> Ian <(E-Mail Removed)> typed:
> > This is almost always a DNS issue
> >
> > Check that the computer has the Domain Controller listed at the
> > primary (first) DNS server.
>
> To clarify, the internal DNS server (AD-integrated, most likely) should be
> the *only* IP address listed for DNS. No public IPs should be in there.
> >
> > Or, take a look at the network settings of the others that do work,
> > and follow.
>
>
>
>

In news:86F12D36-C2D0-48E5-9276-(E-Mail Removed),
SENTHILKUMARAN B <(E-Mail Removed)> typed:
> Hi,
>
> The exact message i got is "Creating the domain name list...Please
> wait."
>
> The client is pointing to a BIND dns which forwards the queries to
> AD DNS server.

I'm certain you're having DNS problems, and given your configuration I don't
think I'm able to address that completely - I'd suggest you post in
microsoft.public.windows.server.dns


>
> thanks,
> Senthilkumaran B
>
> "Lanwench [MVP - Exchange]" wrote:
>
>> In news:14295316-7DB4-446F-93A3-(E-Mail Removed),
>> Ian <(E-Mail Removed)> typed:
>>> This is almost always a DNS issue
>>>
>>> Check that the computer has the Domain Controller listed at the
>>> primary (first) DNS server.
>>
>> To clarify, the internal DNS server (AD-integrated, most likely)
>> should be the *only* IP address listed for DNS. No public IPs should
>> be in there.
>>>
>>> Or, take a look at the network settings of the others that do work,
>>> and follow.