Directory Replication

[mujeeb]

Dear!
I have two domain controller win2k sp4 in same site.
Replication is stoped since few days.When i try to
replicate then manually from active directory site and
services it give me the following error.

"Following error occured during attempt to contact the
domain controller RPC server is unavailable
This contdition may be caused by DNS lookup problem
Please see the following microsoft web site"

Any idea about this problem

Regards

 

[Spale]

How did you configure DNS on NIC on server.If you have a two DC then putt
like this:

Determine which server will be a first and on that NIC putt DNS to reffer of
himsel.
On second server putt DNS on NIC to reffer on first DNS and second DNS putt
to himself.Then restart your server on restart netlogon service to register
DNS and do on cmd promt ipconfig /registerdns.

Hope it helps

 

[mujeeb]

Dear!
I did the same
On first DC which is global catalog server and also dns
server I put first DNS address of its own
and on second DC i put first DNS of first server and
second DNS of its own but problem is still same

If i try to use nslookup from first or second server then
it give me error as
"DNS request timeout
timeout was 2 second.
cananot find (First DC which is DNS server)
Cananot find (Second DC)

If i tried to use nslookup from dns server it give error
that server not found.It seems that problem is in DNS
but if i check DNS event log nothing is there and DNS
service can easily restarted without errors

Hope you will understad situation

Regards ,
Mujeeb

 

[Cary Shultz [A.D. MVP]]

Mujeeb,

have we not already responded to this? Sorry if I am wrong. It just seems
so familiar.

Anyway, the RPC issue is usually indicative of DNS or Networking issues. I
would start by installing the Support Tools on all of your servers ( member
servers, Domain Controllers, et al ). The Support Tools can be found in the
WIN2000 Server CD as well as on the WIN2000 Service Pack CD in the Support |
Tools folder. I would opt for the Service Pack CD as there have been some
modifications along the way. Naturally, you can also download them from the
MS web site at http://www.microsoft.com/downloads.

Just as a general practice I would then run dcdiag /c /v and netdiag /v on
your Domain Controllers. This will give you a good general picture of what
is going on with your network. I might also run netdiag /v on the member
servers. This step is probably not related to your problem, however.

As for the DNS configuration if both DCs are also running DNS ( not clear if
you have two DNS Servers or just the one ) I would set them up as follows:

DC1

DC2
DC1

DC2

DC1
DC2

Also, ensure that you have a Reverse Lookup Zone as well.

I would also make sure that you have the Active Directory Sites and Services
set up properly ( not necessarily related to your problem ) in that you have
the Site created ( by default, WIN2000 will create the
Default-First-Site-Name for you ) with the proper subnets and then associate
each subnet with the appropriate Site.

Look in your DNS Forward Lookup Zone. Underneath that you should see
"yourdomain.com". Under that you should see four subfolders: _msdcs,
_sites, _tcp and _udp. Do you have all four of them? Now look in the
_msdcs folder. Do you see a really long alphanumeric entry for both of your
domain controllers?

Basic steps:
can you ping each Domain Controller via IP Address?
via computer name?
via FQDN?
via <guid>._msdcs.<domain name>?

How about running a nslookup as such:

nslookup
set q=srv
_ldap._tcp.<domain name>

do both Domain Controllers show up in the output?

HTH,

Cary