Problems replicating domain controllers

I'm sure you've done this, but have you checked that the RPC Server is actually running in Services?

Yes. That was the first thing I did.

Have you checked to be sure that the RPC service on either server is not hung or spiking the CPU?  Also, how is your DNS zone set up - AD integrated?  What DNS server is the new Win2K3 server pointing to? Check to be sure it is pointing to the correct server and that you have good comm. between the new server and the DNS server.  That's the basics.  If that's all good, then you need to run dcdiag on the new server to see where it's failing and what's going on.

Hope this helps!

"Now, when I go into AD Sites and Services to set up a replication partner it says this:"  Should's have to do this,.... when you do the DCPROMO, it will automatically configure replication partners for your new DC.  Not sure what you are doing here....

I believe it is AD Integrated. The new 2K3 server is pointing to one of the W2K DCs for DNS. An article I read said to make it point to itself but that didn't do anything. I have ran dcdiag /test:dns and this is what I got:

C:\Documents and Settings\admin acct>dcdiag /test:dns

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\DC01
      Starting test: Connectivity
         The host fd7f4831-8a68-40ad-a8c6-b8513078f3b1._msdcs.<my domain name> could not
be resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
         Although the Guid DNS name
         (fd7f4831-8a68-40ad-a8c6-b8513078f3b1._msdcs.<my domain name>) couldn't be
         resolved, the server name (dc01.xxx.xxx.6.18) resolved to the IP
         address (xxx.xxx.6.11) and was pingable.  Check that the IP address is
         registered correctly with the DNS server.
         ......................... DC01 failed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\DC01

DNS Tests are running and not hung. Please wait a few minutes...

   Running partition tests on : Schema

   Running partition tests on : Configuration

   Running partition tests on : <my domain name>

   Running enterprise tests on : <my domain name>
      Starting test: DNS
         Test results for domain controllers:

            DC: dc01.xxx.xxx.6.18
            Domain: <my domain name>


               TEST: Basic (Basc)
                  Error: No LDAP connectivity
                  Error: The A record for this DC was not found

               TEST: Records registration (RReg)
                  Network Adapter [00000007] Intel(R) PRO/1000 MT Network Connec
tion:
                     Error: Missing A record at DNS server xxx.xxx.6.11 :
                     srvdc01.xxx.xxx.6.18

               Error: Record registrations cannot be found for all the network a
dapters

         Summary of DNS test results:

                                            Auth Basc Forw Del  Dyn  RReg Ext
               ________________________________________________________________
            Domain: <my domain name>
               dc01                      PASS FAIL PASS PASS PASS FAIL n/a

         ......................... <my domain name> failed test DNS

C:\Documents and Settings\admin acct>

Can you all make anything of this?

OK -

1.  After you ran forestprep and adprep, did you make sure that the changes were replicated to all of your Win2K servers before promoting the new server? If not, this could cause problems.

2.  Check your DNS zone and see if the new server has registered itself in the zone and if it shows up correctly on all of your DNS servers.  Also, check the DNS records for DC01 and make sure that they are there and are all correct.  You also need to check the _msdcs.domain.com folder in DNS to see if the GUID name appears and references DC01 correctly. Also, check to see if there is a GUID name entry for the new server correctly referencing that server name.

Please post responses. It looks liked a failed dcpromo to me, but let's see what you come up with on these two things.  Your best bet may be to run dcpromo again and see if you can get this server to gracefully "unpromote" itself and recover from whatever is causing the problem.  If that's successful, then you could try to re-promote it.

I can nslookup an IP and it return the name and vice versa. I don't think we have a failover DNS server. The DCs in AD should all act as DNS servers, right? I ran the dcdiag tool on my existing DCs and they all tested good. Also, I saw in my connectivity tests that the server is showing up as <server name>.<DNS server ip> instead of <server name>.<domain name> Why is this? Would that have something to do with it? When I first loaded the new 2K3 server (before I promoted it to a DC) I added created the Host record in DNS so I know that it is in there.

I have tried to dcpromot (demote) but it doesn't work. It is giving me the same DNS problems.