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

From: Paul (country-air_at_news.postalias)
Date: 07/07/04


Date: Wed, 7 Jul 2004 03:12:31 -0700

Herb - did you have that registry entry, please? Or did
the message from MS scupper it?

Paul

>-----Original Message-----
>"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
>
>There is a feature/setting in XP that causes it to "latch
onto"
>Win2000+ DCs.
>
>It's a registry entry to put it back -- someone will post
it
>today or tomorrow in this thread, but you can look it up
on
>the MS website through search Google with something like:
>
> [ site:microsoft.com XP 2000 | 2003 DC BDC | PDC
registry]
>
>I don't know if that will get it to the top but it will
likely be in
>there somewhere.
>
>Oh, and it's a "feature" because this lets the news
clients get
>their Group Policy and full AD benefits.
>
>--
>Herb Martin
>
>
>"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: Anmeldevorgang in einer Misch Umgebung (inplace Upgrade NT4 --> W2003)
    ... WOHER zum teufel erfahren die Clients in der Zweigstellt und wie vro allen ... es wird ja NT4 PDC emuliert. ... Die melden sich gegen den BDC an ... Der PDC in der Zentrale ist niemals abgeschottet. ...
    (microsoft.public.de.german.win2000.active_directory)
  • Re: RRAS VPN client doesnt get route update
    ... Where does the client get this route change from? ... > to my network. ... some clients don't update their routing ... > connection the default gateway" because the admin net does ...
    (microsoft.public.windows.server.networking)
  • Re: Fallback to NT4 - Clients wont talk to Domain
    ... The registry entry is the one he mentioned and is apparently ... >>> 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)
  • Re: Urgent RRAS wont work Help!
    ... Where you need the extra routing is on the firewall. ... route but whatever config I use it won't route. ... The clients on the ... network have the default gateway set as 184.155.0.80 via DHCP. ...
    (microsoft.public.win2000.ras_routing)
  • Re: DHCP Classless Static Routes
    ... route a 21 bit subnet mask, I must have a moderately complex and large ... many cases subnet the actual Class C, and route between them on a layer 3, ... to implement a subnetmask only for VPN Clints on the VPN Server in the ... Is there anyway to get the VPN Clients in RRAS to assume 192.168.0.0/21 ...
    (microsoft.public.windows.server.networking)