XP and 2K re-joining the domain issue

[Cody Lewis]

I am having a problem with a few machines (not all)

Some XP Pro users receiving an error message similar to
the following:

"Windows cannot connect to the domain either because the
domain controller is unavailable or because your computer
account was not found."

when attempting to log on to the domain. Research of the
MS Knowledge Base indicates that this message may be
caused by Local Group security settings (see Q318266).

Q318266 references NT4.0 domain, but the problem is very
similar. To fix it I can join a workgroup then re-join
the domain, however I am having to do this several times
a day for these folks. The computer account is diabled
(red X in active directory) Any ideas?

I also have a server doing the same thing it isn't a DC.

Thanks in advance
Cody

 

[Michael Johnston [MSFT]]

Who are these machines pointing to for DNS? They should only point at a DNS that is hosting the zone for the AD.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.

 

[Guest]

They are pointing to internal DNS

-----Original Message-----
Who are these machines pointing to for DNS? They should

only point at a DNS that is hosting the zone for the AD.

Thank you,
Mike Johnston
Microsoft Network Support

confers no rights. Use of included script samples are
subject to the

terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all

responses to this message are best directed to the
newsgroup/thread from

 

[Steven L Umbach]

Hi Cody. See this KB link about kerberos and it may be worth trying the registry mod
on one machine. You can also use netdom to reset computer accounts. Also make sure
those machine are configured to use only AD dns servers in tcp/ip properties - never
an ISP dsn server. --- Steve

http://support.microsoft.com/?kbid=244474
http://support.microsoft.com/default.aspx?scid=kb;en-us;216393