again 5781 sp4 single label

[Thomas Toft]

Hi group

I have read now a lot about this problem. My situation looks like
this: 3 DCs ( DNS zone name: abcd, AD name: abcd, NETBIOS name of the
domain: efgh_ijkl )with DNS, one of them forwards to an ISA and the
whole domain still runs in mixed mode. But there is no last NT4-BDC
running.

If I set up a new NT4-BDC in order to rename my domain, it would be
nice to hear about more detailed steps and where there are
difficulties to be expected.

Perhaps I better mention that everything seems to work fine but there
are these 5781-events in the logs...
And there is a trust relationship to another AD-domain called mnop and
this one hosts a SAP/R3-system, also still in mixed mode.
Both domains are upgraded from NT4.

And another question: Why not waiting for Windows Server 2003? I read
that this shall be able to rename ADs...

best regards
toft

 

[Kevin D. Goodknecht [MVP]]

In

Hi group

I have read now a lot about this problem. My situation looks like
this: 3 DCs ( DNS zone name: abcd, AD name: abcd, NETBIOS name of the
domain: efgh_ijkl )with DNS, one of them forwards to an ISA and the
whole domain still runs in mixed mode. But there is no last NT4-BDC
running.

If I set up a new NT4-BDC in order to rename my domain, it would be
nice to hear about more detailed steps and where there are
difficulties to be expected.

Perhaps I better mention that everything seems to work fine but there
are these 5781-events in the logs...
And there is a trust relationship to another AD-domain called mnop and
this one hosts a SAP/R3-system, also still in mixed mode.
Both domains are upgraded from NT4.

And another question: Why not waiting for Windows Server 2003? I read
that this shall be able to rename ADs...

It is true Windows Server 2003 does support domain rename, it is not an easy
task but then neither is rolling the whole thing back to NT4.

You can rid your self of 5781 events by making the reg entries from this KB
on all Win2kSP4 boxes. 300684 - Information About Configuring Windows 2000
for Domains with Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684&FR=1

 

[Thomas Toft]

hi kevin,

thank you for the fast reply. As I expected you tell me to get rid of
5781 events by doing the 300684-thing. But here and there I read that
this is just a bandaid and is not really "empfehlenswert". I don´t
know this in english now. Or shall I just leave everything as it is.
Why changing all the running systems registry? Risk! I can´t evaluate
this. Can you?

thomas

 

[Kevin D. Goodknecht [MVP]]

In

hi kevin,

thank you for the fast reply. As I expected you tell me to get rid of
5781 events by doing the 300684-thing. But here and there I read that
this is just a bandaid and is not really "empfehlenswert". I don´t
know this in english now. Or shall I just leave everything as it is.
Why changing all the running systems registry? Risk! I can´t evaluate
this. Can you?

No this is not risky, it is required if you have a single label domain name
on all clients and servers that must register their addresses in DNS. If you
do not make the registry entry, especially on the DC if it is SP4, it cannot
register its addresses in DNS, which means that eventually if the records
expire or if you change IP addreses, or if you want to add a DC to the
domain, all going to "go down in burning flames". It won't exactly catch on
fire but you get my drift, right?

Your only other choice is to rename the domain, that is not an easy task.
You should probably rename the domain, until you do, this will keep things
working. So in that respect, it is a band aid approach, what are you going
to do until then, you cannot ignore this error!