Re: Fallback to NT4 - Clients won't talk to Domain

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: CJ (chrisj_at_illicom.net)
Date: 07/05/04


Date: Mon, 05 Jul 2004 23:58:53 GMT

You will have to take the WinXP machines and make them a WORKGROUP member,
reboot, then add them to the domain again. Its a pain, but thats what
solved my problem.

"Paul" <country-air@news.postalias> wrote in message
news:25e6001c4627f$57765d00$a601280a@phx.gbl...
> We have been experimenting in the lab with the UPGRADE
> route for converting our NT4 domain to Active Directory.
> One of the reasons we were attracted to this route was the
> claimed ability (in the Migration Cookbook) to fallback to
> the original domain by removing the new W2K DCs and
> replacing with the stored NT4 PDC. This all works OK,
> except...
>
> Any WXP client which has logged in to the new AD doesn't
> want to play with the 'fallen'back' NT4 domain. It says
> that it can't find a [NT4] domain controller. Indeed, the
> client's domain name has 'automatically' changed to the
> name of the AD domain and also the preferred DNS server
> has been altered. The event log says specifically that a
> downgrade is being attempted, and it is necessary for the
> client to rejoin the NT4 domain.
>
> Have we missed something? The Cookbook seems quite
> insistent that you can fall back in this manner! Is there
> an easy way to move all the clients back to the NT4 domain
> without visiting them all?
>
> Incidentally, if we did find a way to rejoin the NT4
> domain for all our clients, then presumably we wouldn't be
> able to re-migrate them to AD without starting from
> scratch, because the upgraded W2K DC would no longer have
> valid machine accounts for the clients (different SIDs)?
>
> Paul



Relevant Pages

  • RE: Can win9x clients connect to new 2003 domain
    ... Windows Server 2003 via NTLM. ... is best if all Windows 95 and Windows 98 clients install the DSClient. ... data on the new DC's and still access files on the NT4 domain?? ... This posting is provided "AS IS" with no warranties, ...
    (microsoft.public.windows.server.migration)
  • Re: Windows XP Pro Client login to Windows NT4 Server (PDC)
    ... It is something of a miracle that W2k clients are fine ... XP clients in an NT4 domain are a little more ... > On trying to connect a Windows XP pro client to a Windows ... > this be reason for the error message. ...
    (microsoft.public.windowsxp.security_admin)
  • DBNETLIB General Network Error
    ... upgrading my NT4 domain so currently running in mixed-mode (One W2003 DC and ... I'm logging in using SQL Server Authentication. ... clients seem to be having less of these issues than my XP/2K clients. ...
    (microsoft.public.sqlserver.security)
  • Re: Fallback to NT4 - Clients wont talk to Domain
    ... > We have been experimenting in the lab with the UPGRADE ... > route for converting our NT4 domain to Active Directory. ... and it's a "feature" because this lets the news clients get ...
    (microsoft.public.win2000.active_directory)