PC doesn't see DC, sort of...

I've got a W2k3 domain controller, and a bunch of WinXP workstations.
Most of them connect to the server without a problem. But there's this
one machine that just won't log into the domain. It's joined to the
domain, but when you try to login, you get a message that it can't see
the domain controller.

But if I logon locally to the workstation, I can map drives to shares on
the DC. I just have to authenticate it once. So it's not a networking
problem - they do connect. It's not really a server problem either. It's
not even a domain problem, because when I manually feed it my creds, it
works fine.

So what's the deal?!

Does this PC list the same DNS server as a PC that does not have this
problem?


hth
DDS

"grep" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I've got a W2k3 domain controller, and a bunch of WinXP workstations. Most
> of them connect to the server without a problem. But there's this one
> machine that just won't log into the domain. It's joined to the domain,
> but when you try to login, you get a message that it can't see the domain
> controller.
>
> But if I logon locally to the workstation, I can map drives to shares on
> the DC. I just have to authenticate it once. So it's not a networking
> problem - they do connect. It's not really a server problem either. It's
> not even a domain problem, because when I manually feed it my creds, it
> works fine.
>
> So what's the deal?!

All the workstations get their DNS info from the same DHCP server, so
yes, it's all the same. Interesting thought, though.

grep

Danny Sanders wrote:
> Does this PC list the same DNS server as a PC that does not have this
> problem?
>
>
> hth
> DDS
>
> "grep" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>
>>I've got a W2k3 domain controller, and a bunch of WinXP workstations. Most
>>of them connect to the server without a problem. But there's this one
>>machine that just won't log into the domain. It's joined to the domain,
>>but when you try to login, you get a message that it can't see the domain
>>controller.
>>
>>But if I logon locally to the workstation, I can map drives to shares on
>>the DC. I just have to authenticate it once. So it's not a networking
>>problem - they do connect. It's not really a server problem either. It's
>>not even a domain problem, because when I manually feed it my creds, it
>>works fine.
>>
>>So what's the deal?!
>
>
>

You might want to verify this by running ipconfig /all on the problem
computer and one without the problem.

Also you might want to post the exact message you get and when you get the
error.


hth
DDS

"grep" <(E-Mail Removed)> wrote in message
news:%23l%(E-Mail Removed)...
> All the workstations get their DNS info from the same DHCP server, so yes,
> it's all the same. Interesting thought, though.
>
> grep
>
> Danny Sanders wrote:
>> Does this PC list the same DNS server as a PC that does not have this
>> problem?
>>
>>
>> hth
>> DDS
>>
>> "grep" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>>
>>>I've got a W2k3 domain controller, and a bunch of WinXP workstations.
>>>Most of them connect to the server without a problem. But there's this
>>>one machine that just won't log into the domain. It's joined to the
>>>domain, but when you try to login, you get a message that it can't see
>>>the domain controller.
>>>
>>>But if I logon locally to the workstation, I can map drives to shares on
>>>the DC. I just have to authenticate it once. So it's not a networking
>>>problem - they do connect. It's not really a server problem either. It's
>>>not even a domain problem, because when I manually feed it my creds, it
>>>works fine.
>>>
>>>So what's the deal?!
>>
>>

Just for grins and giggles, I did verify that I was right about the DHCP
and DNS.

The message is:

"Windows cannot connect to the domain, either because the domain
controller is down or otherwise unavailable, or because your computer
account was not found. Please try again later. If this message continues
to appear, contact your system administrator for assistance."

1. The DC was *not* down.
2. The computer account is in AD. I checked.
3. I am able to connect to domain resources, including the DC, after
logging in locally.
4. I am the system administrator, and I'm apparently being of no help to
myself.

Actually, #4 isn't quite true. I figured out the problem. The computer
account *was* in AD, but it was corrupt. I deleted the object, rejoined
the machine to the domain, and now it works fine.

Thanks for your advice, though.

grep


Danny Sanders wrote:
> You might want to verify this by running ipconfig /all on the problem
> computer and one without the problem.
>
> Also you might want to post the exact message you get and when you get the
> error.
>
>
> hth
> DDS
>
> "grep" <(E-Mail Removed)> wrote in message
> news:%23l%(E-Mail Removed)...
>
>>All the workstations get their DNS info from the same DHCP server, so yes,
>>it's all the same. Interesting thought, though.
>>
>>grep
>>
>>Danny Sanders wrote:
>>
>>>Does this PC list the same DNS server as a PC that does not have this
>>>problem?
>>>
>>>
>>>hth
>>>DDS
>>>
>>>"grep" <(E-Mail Removed)> wrote in message
>>>news:(E-Mail Removed)...
>>>
>>>
>>>>I've got a W2k3 domain controller, and a bunch of WinXP workstations.
>>>>Most of them connect to the server without a problem. But there's this
>>>>one machine that just won't log into the domain. It's joined to the
>>>>domain, but when you try to login, you get a message that it can't see
>>>>the domain controller.
>>>>
>>>>But if I logon locally to the workstation, I can map drives to shares on
>>>>the DC. I just have to authenticate it once. So it's not a networking
>>>>problem - they do connect. It's not really a server problem either. It's
>>>>not even a domain problem, because when I manually feed it my creds, it
>>>>works fine.
>>>>
>>>>So what's the deal?!
>>>
>>>
>