Re: PDC Emulator on Windows 2000

Tech-Archive recommends: Fix windows errors by optimizing your registry

I appreciate all of your advice. I will leave my DC in mixed as we have 8
other locations across the US that each has their own PDC. I do not want to
create a problem if those sites are unable to authenticate with the 2000 AD
domain.

I am in the process of upgrading each to 2000 ADS on a single domain. We
only have 10 or so users at each site.

I am getting this Directory Service warning in the event logs any
suggestions what may cause this? Everything looks correct in DNS and replmon
logs show replication is successful.

Thank you.


Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1265
Date: 10/28/2005
Time: 10:45:44 AM
User: N/A
Computer: SRVDNS01
Description:
The attempt to establish a replication link with parameters

Partition: DC=domain,DC=com
Source DSA DN: CN=NTDS
Settings,CN=SRVDNS03,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=domain,DC=com
Source DSA Address: f2a0c12c-c847-4142-9696-815af4d5a1a3._msdcs.domain.com
Inter-site Transport (if any):

failed with the following status:

The DSA operation is unable to proceed because of a DNS lookup failure.

The record data is the status code. This operation will be retried.
Data:
0000: 4c 21 00 00 L!..





"Ace Fekay [MVP]" wrote:

> In news:8ABF10CC-B0E5-4267-851B-C2189B1DE8FF@xxxxxxxxxxxxx,
> Richard <Richard@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post, which I then
> commented about below:
> > SRV records do exist under the same zone as the DC. We have a single
> > domain.
> >
> > --DESKTOP
> > Microsoft Windows XP [Version 5.1.2600]
> > (C) Copyright 1985-2001 Microsoft Corp.
> >
> > U:\>ipconfig /all
> >
> <snip>
>
> Thanks for posting that. They all look good. One suggestion, on each DC, you
> can point to itself first, and the other as the second entry. I usually like
> to point to the partner as the first entry, and itself as the second. This
> eliminates possible 5781 errors at boot time.
>
> Back to the slow printing, I would assume the print server is a Win2000
> machine, but apparently it seems that NTLM is still being used and it may be
> looking for the old BDC, which is making me think the print server may be an
> NT4 machine?
>
> On one of the clients and on the print server, find out who the logon server
> is:
> echo %logonserver%
> If it is the old BDC, I would suggest to restart both the print server and
> the client, and try it again on both to see if it is now pointing to one of
> the Win2000 DCs.
>
> As far as mixed mode, honestly, if all the NT4 BDCs are gone, you can safely
> change it to Native. Mixed mode's only purpose is for backward compatibility
> with NT4 domain controllers. Mixed mode follows NT4's domain controller
> feature sets and replication behavior, such as no Universal Groups, RAS
> policies, or the ability to nest Global Groups and Universals (which don't
> exist anyway), nor multi-master replication since an NT4 BDC only holds a
> read copy of the database and they look to the Win2000 PDC Emulator for
> replication changes. It has no effect on non-domain controllers.
>
> Ace
>
>
>
>
.