Quantcast
Channel: File Services and Storage forum
Viewing all articles
Browse latest Browse all 13565

FRS on BDC not recieveing replication from PDC

$
0
0

Hi every one! I have been trying trouble shoot my FRS for the past month and a half now, up to this point their is no success

can anyone help me resolve this problem? I have on my network two server (2003), one PDC and a BDC, the event viewer log on the pdc show these messages:

 

The File Replication Service is no longer preventing the computer xxxx_xxx from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL. 

Type "net share" to check for the SYSVOL share

 HOWEVER THE BDC IS SHOWING THESE MESSAGES:

DNS WARNING MESSAGES:

    

The DNS server encountered a packet addressed to itself on IP address 192.168.0.1. The packet is for the DNS name "z.arin.net.". The packet will be discarded. This condition usually indicates a configuration error. 

Check the following areas for possible self-send configuration errors: 
  1) Forwarders list. (DNS servers should not forward to themselves). 
  2) Master lists of secondary zones. 
  3) Notify lists of primary zones. 
  4) Delegations of subzones.  Must not contain NS record for this DNS server unless subzone is also on this server. 
  5) Root hints. 

Example of self-delegation: 
  -> This DNS server dns1.example.microsoft.com is the primary for the zone example.microsoft.com. 
  -> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com, 
  (bar.example.microsoft.com NS dns1.example.microsoft.com) 
  -> BUT the bar.example.microsoft.com zone is NOT on this server. 

Note, you should make this delegation check (with nslookup or DNS manager) both on this DNS server and on the server(s) you delegated the subzone to. It is possible that the delegation was done correctly, but that the primary DNS for the subzone, has any incorrect NS record pointing back at this server. If this incorrect NS record is cached at this server, then the self-send could result.  If found, the subzone DNS server admin should remove the offending NS record. 

FRS LOG ON THE BDC DNS LOG IS ALSO FROM BDC:

  

The File Replication Service is having trouble enabling replication from XXX_XXXA to XXXXSERVERB for c:\windows\sysvol\domain using the DNS name XX

X_XXX.XXX.XXX. FRS will keep retrying. 
 Following are some of the reasons you would see this warning. 

 [1] FRS can not correctly resolve the DNS name XXX_XXX.XXX.XXX from this computer. 
 [2] FRS is not running on XXX_XXX.XXX.XXX. 
 [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers. 

 This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.

Please someone i need your help on this, am very new to win 2003 server my knowledge is basic. (please make the solution instructive for me thanks) from gilliep


Viewing all articles
Browse latest Browse all 13565

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>