Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

DFS Replication just stops

Active Directory, Domain, DNS, WINS, DHCP, SBS, New Releases.

DFS Replication just stops

Postby guest » Thu Jul 29, 2010 10:51 am

Hi

We have setup two new Windows 2008 Standard servers. DFS replication was setup between the two servers. One in site A and the other in site B. Both are DC;s with AD replication working fine. there is also the original Windows 2003 SP1 server is still in site A and is still acting as a DC but plays no role in the DFS replication and never has. The DFS replication between the two Windows 2008 servers is the first time we have ever used DFS.
The connection between two sites is a relatively stable DSL connection with a Max upstream speed of 512Kbps and Max downstream of 4Mbps.

We had a lot of problems with initial replication of the data folder between the two servers in separate sites. So much so that we flew the server from site B down to site A and ran the initial replication over the LAN. Everything looked great after the event log noted the initial replication was complete. Further testing while still on the LAN proved that replication was occurring bi-directional as it was setup.

The site B server was flown back and on-site the next day. Everything continued replication both directions for almost two weeks after that. Then a few days ago, after possible problems with our WAN link, the replication suddenly only started occurring from site B to site A. There is no replication from Site A to B. The Event log shows that DFS is aware of both sites and are still connected as event ID 5004 (DFS inbound connection established) appears. There are a few daily events 5014 (DFS stopping communication) but this is followed almost immediately by event 5004.

I've also checked the staging folder quote and the DFSRPrivate\Staging folder is still less than the quote of 25GB. Also I’ve noticed that trying to manually copy the new data in Site A to Site B simply moves the data out of the data folder and into the ConfiltandDelete folder in DFSRPrivate.


Rebooting all DFS servers and even a fully server reboot (both) doesn't change anything. Is there something I’m missing to check or do to get the data from Site A to start replication to Site B again? and why would Site B data (new and amended) still replicate to Site A?

Any help always appreciated.

Chris
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm

Re: DFS Replication just stops

Postby guest » Thu Jul 29, 2010 10:54 am

Hello Chris,

Since the issue is quite complicated, it is not easy to solid locate the root cause of the DFS replication issue in the WAN link scenario. Please check see if you can get the data from Site A to start replication to Site B again with the following suggestion.

1. We need firstly Check Windows firewall to ensure DFS replication traffic is allowed.

2. Please run the following command on the DFS server to check if can be helpful.

netsh int tcp set global chimney=disabled

netsh int tcp set global RSS=disabled

netsh interface tcp set global autotuninglevel=disabled

3. Please also follow the Microsoft KB article to see if the issue is related to MTU of the network device.

314825 How to Troubleshoot Black Hole Router Issues
http://support.microsoft.com/default.aspx?scid=kb;EN-US;314825

Recommended TCP/IP settings for WAN links with a MTU size of less than 576
http://support.microsoft.com/kb/900926/en-us

4. After you created a domain-based namespace on the first DFS server in Site A, please verify that the other DFS server in Site B has been also specified as an additional server to host the namespace. In this way, we can increase the availability and scalability of the DFS namespace to ensure the DFS replication between the 2 sites.

Steps:

a. Open DFS management console with "dfsmgmt.msc"
b. Right-click on the namespace that you set (ex. \\domain\Public) and then select Add Namespace Server
c. In Namespace server, type the name of another DFS server in Site B to host the namespace, and then click OK.

For more information, please refer to:

Step-by-Step Guide for Distributed File Systems in Windows Server 2008
http://technet2.microsoft.com/windowsserver2008/en/library/cf810bb7-51ed-4535-ab0d-86a7cd862e601033.mspx?mfr=true

5. Moreover, DFS replication depends on the WAN link stability and the Replication schedule of the DFS namespace. Please check and edit the replication schedule of the replication group to see if the schedule is set as full day.

Steps:

a. Open DFS management console with "dfsmgmt.msc"
b. Expand Replication and locate the replication group that you have set
c. Right-click on the replication group
d. Select Edit Replication Group Schedule…

6. Please follow the steps to manually synchronized the target folder on the replication group to check if it works.

a. Open DFS management console with "dfsmgmt.msc"
b. Expand Replication and locate the replication group that you have set
c. Right-click on the replication group and Select "Verify Topology…"
d. Check if the topology for the replication group is fully connected as and data can replicate throughout the topology
f. If yes, you may check the target folder to see if the folder is replicated to the Site B

7. Please also check the inter-site replication schedule to ensure it is configured properly and wait for the replication schedule pass to see whether the file is replicated.

8. If the issue replication still exists, please follow the steps to create diagnostic report.

a. Open "DFS management" console.
b. Expand "Replication" and right-click on the replication group.
c. Select "Create Diagnostic Report"
d. Click "Next" to complete the wizard.

Please note: it will take some time to generate the report, which depends on the network performance.

The Report file is with the extension of.htm in the folder of C:\DFSReports on the DFS server, you may send it to tfwst@microsoft.com and we'd be glad to assist you with that.

Hope this can be helpful.


--------------------------------------------------------------------------------
David Shen - MSFT
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm

Re: DFS Replication just stops

Postby guest » Mon Jun 30, 2014 8:40 pm

TCP off-loading on the network level may be causing the error message which you have posted. So please add these following registry values to all DFSR replications partners to see if it can be helpful.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Value =DisableTaskOffload
Type = DWORD
Data = 1

Value =EnableTCPChimney
Type = DWORD
Data = 0

Value =EnableTCPA
Type = DWORD
Data = 0

Value =EnableRSS
Type = DWORD
Data = 0

Or install latest NIC drive.
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm

Re: DFS Replication just stops

Postby guest » Mon Jun 30, 2014 8:42 pm

please make sure all the necessary DFS ports on all the DFSR replications partners are not blocked by firewall or any other device. For more detailed information about the ports, please refer to the following link:



Service overview and network port requirements for Windows



http://support.microsoft.com/kb/832017#method9
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm

Re: DFS Replication just stops

Postby guest » Mon Jun 30, 2014 8:45 pm

User Action:

=========



1. Please open the ADSIedit.msc console to verify the "Authenticated Users" is set with the default READ permission on the following object:



a. The computer object of the DFS server



b. The DFSR-LocalSettings object under the DFS server computer object



2. After the permissions is set correct, please run "DFSRDIAG POLLAD" to pick up the changes.



3. Another possible reason is that FSRM is configured as some types of files are blocked from DFS replication. When the DFSR filters are not set to match FSRM screens by extension and the files exist on the server before screening, this can lead to degraded DFSR performance and the files will never replicate.



If possible, please remove file screening and reconfigure it to remove files by extension or set a comparable DFSR filter rule to prevent replication attempts.



On the LG*** server, it said that “DFS Replication cannot replicate with partner due to a communication error.” “Check for network connectivity problems, for troubleshooting RPC issues”



Analyze:

=======

This error message generally caused by the network issue, such as:



1. The network connect between the two servers is broken.



2. the necessary ports are blocked by the firewall or other devices.



3. the DNS issue.



User Action :

===========

1. Ping the LE** server from the LG** server to check the network connection.



2. Run nslookup LE** server to check if the DNS name resolution can work properly.



3.Temporarly disable the firewall to check if the issue can be fixed. And double confirm all the necessary DFS ports are not blocked by any other device.



According KCC error message, please refer to the following link, it also tell us the reason and solution:



Event ID 1311: Replication configuration does not reflect the physical network



http://technet.microsoft.com/en-us/libr ... 52(v=ws.10).aspx
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 10191
Joined: Mon Nov 27, 2006 1:10 pm


Return to Windows

Your Ad Here

Who is online

Users browsing this forum: No registered users and 7 guests