RE: AD replication issue
- From: Ryan Hanisco <RyanHanisco@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 13 Jan 2008 20:59:01 -0800
Hi Chris,
If you are using AD Integrated DNS, I would expect these changes to
replicate almost immediately. If you are not using AD Integrated, you should
ask yourself why not. Unless you have a well-defined answer, this should
generally be done.
I would make sure that the servers are able to ping the domain by FQDN, not
just by name. This would result in the SRV records being hit and generally
the PDCe will be returned. If this is not working, you will want to look at
the search scopes and the DNS servers that might be in there as forwarders.
Finally, you can go through the DNS manually to look for the SRV records
that should be there and to ensure that zone transfers are appropriately
configured. You might also want to run diagnostics with REPLMON, DCDIAG, and
NETDIAG to get more information.
Let us know and we'll be there to help!
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
http://www.techsterity.com
Chicago, IL
Remember: Marking helpful answers helps everyone find the info they need
quickly.
"Chris Meehan" wrote:
So the situation is this.....
in a remote site a new domain controller was installed and promoted. The
existing server at that location was demoted after intrasite replication took
place. For the sake of questioning the new domain controller will be called
DC2 and the old will be called DC1.
Problem is this...
On the new domain controller (DC2) at the remote site, everything looks good.
New server shows up in Domain Controllers OU, all DNS records registered
correctly, including CNAME. Old server shows as member server in the
computers OU.
On every other domain controller in the domain, It still looks as if nothing
had taken place as far as demoting and promoting. In the Domain Controllers
OU the old server (DC1) still shows.
The problem is with replication.. Inbound replication to the new DC2 server
at the remote site is working fine, however replication from the remote
domain controller inbound to servers at the hub site will not work.
I have verified all DNS test via dcdiag and tried using the repadmin /add
command to add an inbound connection object using GUIDS but get an error
stating,
"The DSA operation is unable to proceed because of a DNS lookup failure"
Error 8524.
I can ping both ways via host name, and nslookup from the server that I am
running the repadmin /add command from shows the correct ip. Kinda at a loss
here with this one and would like to try to prevent having to demote then
repromote the domain controller again. Any suggestions? thanks in advance.
Chris
- Prev by Date: Re: promoting a member server to DC
- Next by Date: RE: AD Sid History
- Previous by thread: Re: AD replication issue
- Next by thread: Re: Remove Guest From Administrator Group(Server 2003)
- Index(es):
Relevant Pages
|
