AD Replication Issue

[Brad Higgins]

I have a native 2000 environment with 1 DC as the Primary
domain controller emulator role and with and active
directory integrated zone in DNS.

I have managed to upgrade another of my member servers to
domain controller but it didn't finish replicating the
domain across.

When I try to do a force replication I get an error RPC
Server unavaliable, and then points it to be a DNS issue.
My DNS zone file includes the _mcds, _tcp, _udp and _sites
folders and appears set up fine and is the only DNS server
in my new domain controllers NIC configuration.

Through active directory users and computers when I try to
connect to domain controller (from my PDC) I get the same
error as above. But from my new domain controller I can
connect to both, and it shows that the new DC does not
have the same OU's as the PDC.

Can anyone shed some light?

cheers

Brad

 

[Matjaz Ladava [MVP]]

Is your server actualy pointing to your internal DNS server ? Check your dns
configuration against
%systemroot%\system32\config\netlogon.dns file. USe nslookup to verify that
you can resolve your hostname.

--
Regards

Matjaz Ladava, MCSE (NT4 & 2000), Windows MVP
(e-mail address removed)
http://ladava.com

 

[Herb Martin]

Most such problems are either cause by (or complicated by)
DNS problems -- so check and fix those first and see if anything
else remains.

1) DNS dynamic
2) ALL internal machines set as CLIENTS of the internal, dynamic
DNS server ONLY -- including DCs (and the DNS server)
3) Restart NetLogon on DC if you fix these
4) At least two tags (e.g. Domain.Com, not Domain) in the DNS name
5) All machine set to use the correct DNS name in System Control Panel

Don't set machines to use both your internal DNS servers and some other
DNS servers, even if they have multiple NICs.

Let the internal DNS server forward if you need to resolve on the Internet.