Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 349
  • Last Modified:

W2K Server Replication Problem

I have two servers that are set up as domain controllers.  AS1, and AS2.  AS1 is the "pdc."  I'm not getting any DNS errors and everything looks fine in the zones, as in, the _msdcs, _sites, _tcp, and _udp folders were created.  Both servers have entries in both forward and reverse lookup and they are correct.  I can also ping both servers from eachother.  AD is replicating fine.  The netlogon share is what's not replicating.

When I restart the FRS I get and Event ID 13508:
The File Replication Service is having trouble enabling replication from AS1 to AS2 for c:\winnt\sysvol\domain using the DNS name as1.prendie.edu. FRS will keep retrying.

I also get an Event ID 3019 from source MXrSmb:
The redirector failed to determine the connection type.

Actually, this is new, I just tried it (restarting netlogon and frs) and got an Event ID 5774 from Netlogon:
Registration of the DNS record '5d59bc26-09da-40dc-a422-111c1b08467e._msdcs.prendie.edu. 600 IN CNAME as2.prendie.edu.' failed with the following error:
DNS RR set that ought to exist, does not exist.  .

I can't get this 2nd domain controller off because when I run dcpromo it says:
The operation failed because:
The Directory Service failed to replicate off changes made locally.
"The DSA operation is unable to proceed because of a DNS lookup failure."

Any help is appreciated.
0
salvagbf
Asked:
salvagbf
  • 3
  • 2
1 Solution
 
exx1976Commented:
What machine has your DNS server on it?  Are they both DNS servers?  Are they ocnfigured to point to each other, or themselves??
0
 
salvagbfAuthor Commented:
When I originally set it up, I pointed the first to itself for DNS and ran dcpromo and let it set up the DNS on itself.  Then I installed DNS on the second as a secondary DNS server with it pointing only to itself for DNS and ran dcpromo.  I noticed after this that it added another forward lookup for prendie.com when I had specifically only set prendi.edu so I deleted the prendie.com zone.  I'm guessing that's where my problems came from buy that doesn't make any sense.

Right now both dc's have eachother as the second DNS in the IP config.  I've tried uninstalling DNS on the second server but when I reinstall it it immediately comes back up with the previous DNS config.  I was thinking that I shouldn't have set up the second DNS as a secondary but as another standard DNS server...
0
 
exx1976Commented:
They should both be set up as AD integrated zones, and they should point to each other for the primary DNS, otherwise you end up with the "Island effect"..  And if your second machine came up with prendie.com, then it sounds to me like you inadvertantly set it up to be prendie.com instead of prendie.edu..   Check the Network tab of My Computer properies and verify that they are both members of Prendie.edu, and then change your DNS to be AD integrated...
0
 
salvagbfAuthor Commented:
Wow, don't I feel stupid.  The only problem  was that the reverse lookup zone was running as a standard secondary, everything else was AD integrated.  Chaged that to AD integrated and pointed the servers to eachother's DNS and it's all working.  Thanks so much exx.
0
 
exx1976Commented:
Glad to help.

-exx
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now