W2kPro/XP AD detect

[BillJ]

We're lab testing our 2003 server AD environment for
rollout this december. The lab setup is: NT4 domain
(pdc/2bdc's) with BIND DNS (static IP for all) configured
according to KB 255913. A 2003 server (non-AD) is running
DNS to take care of the underscore 'zones'. Other nodes
in the lan include w2k server/pro and xp.
I did an in-place upgrade on the pdc that seemed to go
smoothly.
QUESTION: At what point exactly do the W2k and xp pro
workstations and the w2k server see and authenticate with
the AD? And once they've authenticated with AD, is there
any going back (authenticating) to NT for those clients?
Thanks for your attention.

 

[SaltPeter]

We're lab testing our 2003 server AD environment for
rollout this december. The lab setup is: NT4 domain
(pdc/2bdc's) with BIND DNS (static IP for all) configured
according to KB 255913. A 2003 server (non-AD) is running
DNS to take care of the underscore 'zones'. Other nodes
in the lan include w2k server/pro and xp.
I did an in-place upgrade on the pdc that seemed to go
smoothly.
QUESTION: At what point exactly do the W2k and xp pro
workstations and the w2k server see and authenticate with
the AD? And once they've authenticated with AD, is there
any going back (authenticating) to NT for those clients?
Thanks for your attention.

It's recommended to keep an NT4 BDC offline for at least a week in the case
you want to revert to an NT4 netbios domain. Without this failsafe
procedure, the clients have nothing to revert to.

 

[Guest]

A spare bdc was indeed taken off line for just that
purpose. However, that's not my question. I need to know
what wk2 pro and xp users need to do to authenticate with
AD. Also, once they're authenticated in the AD, is it
possible for those clients to once again use ntlm
authentication?
Our netbios and dns namespaces are named differently:
netbios=name1
dns=name2