Re: Cannot Logon to Domain, only new PC

From: Mark Ramey (mramey_at_online.microsoft.com)
Date: 04/19/04 

Date: Mon, 19 Apr 2004 02:14:23 -0500

Dan,

Once you reset the computer account in AD Users and Computers you have to
disjoin the machine from the domain and rejoin it. This may be the reason
why you were seeing the errors you were seeing. This is documented in the
Help file for 2000 under Resetting Accounts.

Mark

"Dan" <anonymous@discussions.microsoft.com> wrote in message
news:0cce01c425d9$a19209d0$a501280a@phx.gbl...
> >Reset the computer to a workgroup. Delete the old
> computer account(s) from
> >the server. Rejoin the domain. Does that help?
>
> Thanks for the advise, this worked. Don't know why i
> didn't think to try that, i guess one shouldn't really
> have to do this. I did try disabling/enabling and
> resetting the computer account, and also manual creating
> a "new" one. hmmmm stupid windows :)
>
>
> >-----Original Message-----
> >Dan wrote:
> >> I have a new PC on the domain.
> >>
> >> The user first connected the PC to the network her self
> >> (grrrrrr). The PC name being "Kellie", the replaced PC
> >> also "Kellie". The were both on the domain and logged
> in
> >> (same user same PC name) and working. Thinking to
> avoid
> >> issues until the OLD PC was completely removed from the
> >> network i renamed it to "KellieOLD".
> >> Doing this stopped the "OLD" PC logging onto the domain
> >> with the error
> >> "Windows cannot connect to the domain or because domain
> >> controller is unavailable or your computer account was
> >> not found."
> >> This "KellieOLD" does have an automaticly generated
> entry
> >> on the "Computers" section of the AD.
> >>
> >> NOW the new PC "Kellie" reports the same error and the
> >> prevoius entry of "Kellie" in "Computers" under the AD
> is
> >> gone (perhaps automaticly changed with the old PC
> renamed
> >> to KellieOLD). I added an entry "kellie" to Computer
> in
> >> the AD but still no luck.
> >>
> >> Any ideas would be great, i've yet to reset the server,
> >> but this will be next save upsetting the users.
> >
> >Reset the computer to a workgroup. Delete the old
> computer account(s) from
> >the server. Rejoin the domain. Does that help?
> >
> >>
> >> Dan
> >
> >
> >.
> >

Relevant Pages

  • Re: Only 1 computer denied access to DC
    ... Unjoin and rejoin creates a new sid which forces a reset. ... d:\i386\adminpak.msi (Server tools for remote management of servers) ...
    (microsoft.public.windows.server.active_directory)
  • Re: win2000 pro client cannot join mixed mode ActiveDirectory after being deleted
    ... into a workgroup and then rejoin the domain. ... > A computer account was deleted from the Active Directory, ... Once loaded this server was promoted using dcpromo, ... it became clear once the Windows 2000 pro client was ...
    (microsoft.public.windows.server.active_directory)
  • Re: Duplicate MyDocuments root
    ... The problem is that I had to rebuild the server from scratch, ... Rejoin domain ... Login as USER (create root folder) logout ... > try resetting the domain computer account and rejoining it. ...
    (microsoft.public.windows.server.general)
  • Re: Problems rejoining Nt Member server to Win2003 Domain
    ... also try deleting the computer account outright. ... But now the sever will not rejoin the ... Suspect it may be a SID issue, ... WAN), and can browse okay, but server refuses to join. ...
    (microsoft.public.windows.server.general)
  • Re: Cannot Logon to Domain, only new PC
    ... >Reset the computer to a workgroup. ... Rejoin the domain. ... >> Any ideas would be great, i've yet to reset the server, ...
    (microsoft.public.win2000.active_directory)