Re: 2008 replication

Hello Cindy,

Normally the initial replication is done during the promotion of a DC. So the AD database is replicated and the sysvol and netlogon. To make sure that this occur correct, configure the new DC to use only one of the 2003 DC/DNS servers on the NIC as preferred, no other. Also you should install DNS on the new DC's for redundancy and also if you will remove the old ones in any time you have available DNS servers.

On the new DC's run dcdiag /v and post the output here. Also do the same from the old ones.

The ipconfig /all looks ok, if the new DC's are not DNS servers.

Did you rund dcdiag /v, netdiag /v and repadmin /showrepl on the 2003 DC's to check that they are healthy and replicate correct before adding the new ones?

Are any firewall running on the 2003/2008 machines?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


Hi -
I have an issue I am stuck on... I'll try to keep the explaintion
fairly
short.
I have 2 new 2008 servers that I have added AD to. These are being
added to
a Domain that currently has 2 -2003 DC's. I did the Adprep for
forest,
domain and GPs.
Everything went OK until it was time to replicate.... here is what I
get...
(by the way - the 2 2003 DCs have DNS on them)
When I try to initiate a replication form either 2008 DC- to any
server - I
get this error - "the following occured during attempt to contact
(current
server name) "RPC server not avaialble"
When initiating from the 2003 server - they replicate to each other
fine.
when I try to replicate to either 2008 server - I get "naming context
is in
the process of being removed or is not replicated for the speific
server."
I have looked at a lot of the DNS problem solving ideas... but
everything looks to be OK with DNS. Could this be a 2008 issue rather
then a DNS issue??? Has anyone run into this when introducing 2008
into the Domain. Any help or ideas would be greatly appreciated!!!
thanks in advance!!!

ALso, the only odd thing I noticed was when installing the 2nd DC, a
message said it ofund 3 DNS servers in the Domain. there are only 2.
Is there some cmd to identify the servers thought to be hosting DNS???

thanks - again - Cindy



.

Relevant Pages

  • Re: DNS signature failed to verify error
    ... Since DNS on both servers only contains the NS record of the SBS ... the _msdcs.domain.local zone on both DNS's are set to replicate to "All DNS ...
    (microsoft.public.windows.server.dns)
  • Re: 2008 replication
    ... Did not realize anything about time problem. ... With "peers" you can set the time source, either DNS name or an ip address from a reliable time source. ... one of the 2003 DC/DNS servers on the NIC as preferred, ... When initiating from the 2003 server - they replicate to each other ...
    (microsoft.public.windows.server.active_directory)
  • Re: Failure to replicate - new 2003 sp2 DC
    ... are these servers separated by FW? ... As I said, zntr points to itself for DNS with nar as alternate, and Nar ... trying to get to replicate. ... Nar fails netdiag's domain membership test with The system ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication Problems
    ... DNS is the most common reason for failure to replicate. ... > servers being unreachable). ... Publish sufficient site connectivity information such that the system ...
    (microsoft.public.win2000.active_directory)
  • NLB server 2003 content maintenance?
    ... The easiest solution was to NLB the web servers and make ... app that will replicate files in real time one direction, ... >We're planning to have a dozen or so web sites (lots of ... >imagine we would have a back-end machine with the web ...
    (microsoft.public.windows.server.clustering)