PDC Emulation

  • Thread starter Thread starter NL
  • Start date Start date
N

NL

Hi. I just upgraded my first NT4.0 PDC to W2K DC with PDC
Emulation enabled to temporarily support current NT4.0
BDC for synchronization purposes. The BDC will be
upgraded to W2K soon after. All was working as expected
but after installing SP4 on W2K, server manager on the
BDC sees this server also as a BDC instead of a PDC. A
PDC no longer exist. We tried uninstalling SP4 on the
W2K server with no luck. Any thoughts. Please assist.
Thanks ...
 
Hi. I just upgraded my first NT4.0 PDC to W2K DC with PDC
Emulation enabled to temporarily support current NT4.0
BDC for synchronization purposes.

Sorry, what are you talking about? The PDC emulator is one of 5 FSMOs
needed to run a forrest.
I think you mean "mixed mode".

Ciao, Walter
 
Apologies if I wasn't clear. Basically, after installing
SP4 on the DC, the NT4 BDC stopped seeing this server as
a PDC. Is that normal? Asking because before SP4 was
installed, the BDC was able to view the DC as PDC.
 
I may be clear again. Seems like the link refers to NT4
w/SP4? I meant the following.

Server1: NT 4.0 BDC server w/ SP6
Server2: Currently upgraded NT4 PDC to W2K DC w/SP4
 
I may be clear again. Seems like the link refers to NT4
w/SP4? I meant the following.

Server1: NT 4.0 BDC server w/ SP6
Server2: Currently upgraded NT4 PDC to W2K DC w/SP4

I know. The default behaviour for authentification was changed by
Windows 2000 SP4. NT 4.0 SP4 was the first version to be able to
communicate through NTLMv2.
The article describes how to change NT to switch from LM
authentification. The same keys are used (AFAIK) in Win2000. You have
to match both ends to use NTLMv2 (recommended) or anything else.

Ciao, Walter
 
NL said:
Hi. I just upgraded my first NT4.0 PDC to W2K DC with PDC
Emulation enabled to temporarily support current NT4.0
BDC for synchronization purposes. The BDC will be
upgraded to W2K soon after.

PDC Emulation will always be enabled in a properly functioning
Win2000/Win2003 domain.

It is slightly misnamed since it does a few jobs other than JUST
provide PDC service to BDCs or even to legacy clients.

PDC Emulator is needed even in Native Mode.
All was working as expected
but after installing SP4 on W2K, server manager on the
BDC sees this server also as a BDC instead of a PDC. A
PDC no longer exist. We tried uninstalling SP4 on the
W2K server with no luck. Any thoughts. Please assist.
Thanks ...

How do you know that is "sees it as a BDC"? What tool, what
message?

Does AD Users/Groups show it as the PDC emulator in roles?

You probably just messed up the name resolution (WINS perhaps
even) and now the BDC cannot find the PDC EMulator at all (or
vice versa.)
 
How do you know that is "sees it as a BDC"? What tool,
what

From Server Manager on the NT4 BDC. No PDC existed after
installing SP4 on the W2K DC. It was fine prior to the
SP4 installation.
 
nl said:
From Server Manager on the NT4 BDC. No PDC existed after
installing SP4 on the W2K DC. It was fine prior to the
SP4 installation.

The real question is does it replicate? (Server Manager is not really
"the BDC" itself but just a program that might not be getting it right.
Server Manager can even run on an NT4 or W9x workstation.)

Have you checked AD Users/Computers to ensure you have the
PDC Emulator role working as you believe?
 
Open AD users and computers. Do a propterties on the
domain and select operation masters. Is the PDC role
assigned to the right computer?
If it is just make sure that the two dc's are replicating.
 
That's what I'm getting at. The BDC server sees no PDC,
therefore it cannot replicate. I think Walter Schulz
might be going in the right direction. I'll give that a
trying first thing Monday. Thanks ...
 
On the DC, yes it is assigned to the right computer but
on the NT4 BDC's Server Manager, no the PDC disappeared
after apply SP4 on W2K's DC. That's the problem, cannot
replicate. I'm trying to find out if SP4 has anything to
do with it. Thanks ...
 
Back
Top