Solved

Replicatin problem with server 2003.

Posted on 2008-06-10
8
2,704 Views
Last Modified: 2008-09-05
Hi guys.

I have problems replicating to another server of mine.

Can anyone advise me as to how to  rectify it
I have check dns.

msg09sgp run dcdiag and netdiag fine.

problem is msg07sgp which i have posted below.

How do I resolve the rpc server is unavailable problem.
RPC service is up and running on msg09sgp
Thanks
Domain Controller Diagnosis
 

Performing initial setup:

   Done gathering initial info.
 

Doing initial required tests

   

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

      Starting test: Connectivity

         ......................... MSG07SGP passed test Connectivity
 

Doing primary tests

   

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

      Starting test: Replications

         [Replications Check,MSG07SGP] A recent replication attempt failed:

            From MSG09SGP to MSG07SGP

            Naming Context: DC=ForestDnsZones,DC=lfrg,DC=local

            The replication generated an error (1256):

            The remote system is not available. For information about network troubleshooting, see Windows Help.

            The failure occurred at 2008-06-11 10:59:29.

            The last success occurred at 2008-06-10 15:42:39.

            22 failures have occurred since the last success.

         [MSG09SGP] DsBindWithSpnEx() failed with error 1722,

         The RPC server is unavailable..

         [Replications Check,MSG07SGP] A recent replication attempt failed:

            From MSG09SGP to MSG07SGP

            Naming Context: DC=DomainDnsZones,DC=lfrg,DC=local

            The replication generated an error (1256):

            The remote system is not available. For information about network troubleshooting, see Windows Help.

            The failure occurred at 2008-06-11 10:59:29.

            The last success occurred at 2008-06-10 15:42:40.

            27 failures have occurred since the last success.

         [Replications Check,MSG07SGP] A recent replication attempt failed:

            From MSG09SGP to MSG07SGP

            Naming Context: CN=Schema,CN=Configuration,DC=lfrg,DC=local

            The replication generated an error (1722):

            The RPC server is unavailable.

            The failure occurred at 2008-06-11 11:00:11.

            The last success occurred at 2008-06-04 16:00:14.

            166 failures have occurred since the last success.

            The source remains down. Please check the machine.

         [Replications Check,MSG07SGP] A recent replication attempt failed:

            From MSG09SGP to MSG07SGP

            Naming Context: CN=Configuration,DC=lfrg,DC=local

            The replication generated an error (1722):

            The RPC server is unavailable.

            The failure occurred at 2008-06-11 10:59:50.

            The last success occurred at 2008-06-10 15:50:31.

            51 failures have occurred since the last success.

            The source remains down. Please check the machine.

         [Replications Check,MSG07SGP] A recent replication attempt failed:

            From MSG09SGP to MSG07SGP

            Naming Context: DC=lfrg,DC=local

            The replication generated an error (1722):

            The RPC server is unavailable.

            The failure occurred at 2008-06-11 11:07:49.

            The last success occurred at 2008-06-10 15:54:50.

            32 failures have occurred since the last success.

            The source remains down. Please check the machine.

         REPLICATION-RECEIVED LATENCY WARNING

         MSG07SGP:  Current time is 2008-06-11 11:13:33.

            DC=ForestDnsZones,DC=lfrg,DC=local

               Last replication recieved from MSG09SGP at 2008-06-10 15:42:39.

            DC=DomainDnsZones,DC=lfrg,DC=local

               Last replication recieved from MSG09SGP at 2008-06-10 15:42:40.

            CN=Schema,CN=Configuration,DC=lfrg,DC=local

               Last replication recieved from MSG09SGP at 2008-06-04 16:00:14.

            CN=Configuration,DC=lfrg,DC=local

               Last replication recieved from MSG09SGP at 2008-06-10 15:50:31.

            DC=lfrg,DC=local

               Last replication recieved from MSG09SGP at 2008-06-10 15:54:50.

         ......................... MSG07SGP passed test Replications

      Starting test: NCSecDesc

         ......................... MSG07SGP passed test NCSecDesc

      Starting test: NetLogons

         ......................... MSG07SGP passed test NetLogons

      Starting test: Advertising

         ......................... MSG07SGP passed test Advertising

      Starting test: KnowsOfRoleHolders

         ......................... MSG07SGP passed test KnowsOfRoleHolders

      Starting test: RidManager

         ......................... MSG07SGP passed test RidManager

      Starting test: MachineAccount

         The account MSG07SGP is not trusted for delegation.  It cannot replicate.

         ......................... MSG07SGP failed test MachineAccount

      Starting test: Services

         ......................... MSG07SGP passed test Services

      Starting test: ObjectsReplicated

         ......................... MSG07SGP passed test ObjectsReplicated

      Starting test: frssysvol

         ......................... MSG07SGP passed test frssysvol

      Starting test: frsevent

         There are warning or error events within the last 24 hours after the
 

         SYSVOL has been shared.  Failing SYSVOL replication problems may cause
 

         Group Policy problems. 

         ......................... MSG07SGP failed test frsevent

      Starting test: kccevent

         ......................... MSG07SGP passed test kccevent

      Starting test: systemlog

         ......................... MSG07SGP passed test systemlog

      Starting test: VerifyReferences

         ......................... MSG07SGP passed test VerifyReferences

   

   Running partition tests on : ForestDnsZones

      Starting test: CrossRefValidation

         ......................... ForestDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom

         ......................... ForestDnsZones passed test CheckSDRefDom

   

   Running partition tests on : DomainDnsZones

      Starting test: CrossRefValidation

         ......................... DomainDnsZones passed test CrossRefValidation

      Starting test: CheckSDRefDom

         ......................... DomainDnsZones passed test CheckSDRefDom

   

   Running partition tests on : Schema

      Starting test: CrossRefValidation

         ......................... Schema passed test CrossRefValidation

      Starting test: CheckSDRefDom

         ......................... Schema passed test CheckSDRefDom

   

   Running partition tests on : Configuration

      Starting test: CrossRefValidation

         ......................... Configuration passed test CrossRefValidation

      Starting test: CheckSDRefDom

         ......................... Configuration passed test CheckSDRefDom

   

   Running partition tests on : lfrg

      Starting test: CrossRefValidation

         ......................... lfrg passed test CrossRefValidation

      Starting test: CheckSDRefDom

         ......................... lfrg passed test CheckSDRefDom

   

   Running partition tests on : BLS

      Starting test: CrossRefValidation

         This cross-ref has a non-standard dNSRoot attribute.
 

          Cross-ref DN:
 

         CN=bb20e6a6-c2bb-42fd-95b3-139e8c26bfc8,CN=Partitions,CN=Configuration,DC=lfrg,DC=local
 

          nCName attribute (Partition name): DC=BLS,DC=SITE
 

          Bad dNSRoot attribute: msg07sgp.lfrg.local
 

          Check with your network administrator to make sure this dNSRoot
 

         attribute is correct, and if not please change the attribute to the
 

         value below.
 

           dNSRoot should be: BLS.SITE 

            It appears this partition (DC=BLS,DC=SITE) failed to get completely
 

            created.  This cross-ref
 

            (CN=bb20e6a6-c2bb-42fd-95b3-139e8c26bfc8,CN=Partitions,CN=Configuration,DC=lfrg,DC=local)
 

             is dead and should be removed from the Active Directory. 

         ......................... BLS failed test CrossRefValidation

      Starting test: CheckSDRefDom

         ......................... BLS passed test CheckSDRefDom

   

   Running enterprise tests on : lfrg.local

      Starting test: Intersite

         ......................... lfrg.local passed test Intersite

      Starting test: FsmoCheck

         ......................... lfrg.local passed test FsmoCheck

Open in new window

0
Comment
Question by:moneywell
  • 4
  • 3
8 Comments
 
LVL 13

Expert Comment

by:rhinoceros
ID: 21757897
>>Starting test: frsevent
>>         There are warning or error events within the last 24 hours after the
>>          SYSVOL has been shared.  Failing SYSVOL replication problems may cause
>>          Group Policy problems.

First, You are able to connect the NETLOGON share! (\\SERVER\netlogon)  ? If no, you need to perform a D4 (auth-restore).

"How to rebuild the SYSVOL tree and its content in a domain"
http://support.microsoft.com/kb/315457


Second, any error log message found ?
0
 

Author Comment

by:moneywell
ID: 21758058
Hi rhinoceros,

netlogon can be shared.

Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1888). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
 (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
In-site:
msg07sgp.lfrg.local      CDG 1 7 7 1 0 1 1 7 1
msg09sgp.lfrg.local      CDG 1 0 0 1 0 0 0 0 0
 Out-of-site:
 

No big problems

The DNS server was unable to complete directory service enumeration of zone lfrg.local.  This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it.  Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is "". The event data contains the error.

The File Replication Service is having trouble enabling replication from MSG09SGP to MSG07SGP for c:\windows\sysvol\domain using the DNS name msg09sgp.lfrg.local. FRS will keep retrying.
 Following are some of the reasons you would see this warning.
 
 [1] FRS can not correctly resolve the DNS name msg09sgp.lfrg.local from this computer.
 [2] FRS is not running on msg09sgp.lfrg.local.
 [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
 
0
 
LVL 13

Expert Comment

by:rhinoceros
ID: 21758246
"netlogon can be shared."
From ALL DCs, those are also shared ?

Because you have an error from dcdiag and netdiag
>>Starting test: frsevent
>>         There are warning or error events within the last 24 hours after the
>>          SYSVOL has been shared.  Failing SYSVOL replication problems may cause
>>          Group Policy problems.


Further, plesae check you site link. Do you have any manual connection objects? If so, check the transport type, it might be incorrectly defined as SMTP. May need to reconfigure the sites to use an IP link.  Even verify with REPLMON/ REPADMIN.

Some information
http://www.eventid.net/display.asp?eventid=13508&eventno=349&source=NtFrs&phase=1
http://www.eventid.net/display.asp?eventid=13508&eventno=6585&source=FRS&phase=1
0
 

Author Comment

by:moneywell
ID: 21758282
Ok i will test it, will revert back to you.
0
Free Trending Threat Insights Every Day

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 

Author Comment

by:moneywell
ID: 21766034
Hi my replication is ok now.
Checked frs and frs is ok now after i restarted the service.

0
 

Author Comment

by:moneywell
ID: 21766041
Last question
How do i fix this

unning partition tests on : BLS
      Starting test: CrossRefValidation
         This cross-ref has a non-standard dNSRoot attribute.

          Cross-ref DN:

         CN=bb20e6a6-c2bb-42fd-95b3-139e8c26bfc8,CN=Partitions,CN=Configuration,DC=lfrg,DC=local

          nCName attribute (Partition name): DC=BLS,DC=SITE

          Bad dNSRoot attribute: msg07sgp.lfrg.local

          Check with your network administrator to make sure this dNSRoot

         attribute is correct, and if not please change the attribute to the

         value below.

           dNSRoot should be: BLS.SITE
            It appears this partition (DC=BLS,DC=SITE) failed to get completely

            created.  This cross-ref

            (CN=bb20e6a6-c2bb-42fd-95b3-139e8c26bfc8,CN=Partitions,CN=Configuration,DC=lfrg,DC=local)

             is dead and should be removed from the Active Directory.
         ......................... BLS failed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... BLS passed test CheckSDRefDom
   
0
 
LVL 13

Accepted Solution

by:
rhinoceros earned 300 total points
ID: 21766143
-Ensure that the DNS settings of the DC/DNS server points to itself in the TCP/IP settings.
-Restart the DNS Server service.

Now, try running the dcdiag and netdiag again. Check if the error still exists.
0
 

Expert Comment

by:afamm
ID: 22397999
I have checked the DNS entries on both DC's and realised that the primary dns entry for the 1st DC has 127.0.0.1 but i have changed it to the correct ip though 127.0.0.1 meant same. Restarted DNS and ran dcdiag but still got the same error.
0

Featured Post

Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

Join & Write a Comment

So you have two Windows Servers and you have a directory/folder/files on one that you'd like to mirror to the other?  You don't really want to deal with DFS or a 3rd party solution like Doubletake. You can use Robocopy from the Windows Server 200…
I've always wanted to allow a user to have a printer no matter where they login. The steps below will show you how to achieve just that. In this Article I'll show how to deploy printers automatically with group policy and then using security fil…
This video shows how to remove a single email address from the Outlook 2010 Auto Suggestion memory. NOTE: For Outlook 2016 and 2013 perform the exact same steps. Open a new email: Click the New email button in Outlook. Start typing the address: …
This tutorial demonstrates a quick way of adding group price to multiple Magento products.

757 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

23 Experts available now in Live!

Get 1:1 Help Now