DFS-R on Server 2008 mode

I just set up DFS-R in Server 2008 mode with two servers in a mesh topology. The two servers are in different AD sites but there is a 50Mbps PTP line between them.

Server A syncs perfectly with Server B in a matter of one second. However Server B does not sync with Server A. Or it does about 10% of the time.

I've rebooted a few times as well. Any ideas what could be causing this?

No firewalls are being used in-between the two servers.
fina27Asked:
Who is Participating?
 
fina27Author Commented:
I opened a Microsoft support ticket for the issue. The resolution was to stop the DFS-R service. Delete the replication group, then delete the DFSrprivate folders on both source and target for the folder. Then start the DFS-R service. Recreate the replication group and begin initial sync. I havent had any delays since I did this.
0
 
Vince GlissonOwnerCommented:
Are any of the server involved SBS?
0
 
fina27Author Commented:
Nope. Both are Server 2008 Std edition. However one server is 32-bit and the other is 64-bit. I don't think that matters though.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Vince GlissonOwnerCommented:
Are the they in the same Domain? I see that you said differnet sites so need clarification.
0
 
fina27Author Commented:
Yep same domain. But different sites and subnets.
0
 
fina27Author Commented:
i just figured out its only happening to a few folders. I only have 5 total DFS folders, and its only doing it to two of them. Maybe something to do with the Dfsrprivate folders?
0
 
Vince GlissonOwnerCommented:
Yes i think your on to something. Any difference in the persmissions from folders that sync and folders that do not?
 
 
0
 
fina27Author Commented:
No difference at all. These are pretty public folders.... so the permissions are pretty much wide open. I tried increasing the staging quota from 4GB to 20GB considering these are large folders that are between 70GB-100GB. But that didnt work either.
0
 
Vince GlissonOwnerCommented:
This article is about want can happen when there is left over FRS data when you move to  DFS-R, maybe the problem...
http://www.eggheadcafe.com/software/aspnet/29529027/dfsr--event-id-6402--df.aspx
What error are you getting in event viewer?
Any encrypted data in the folders in question?
0
 
fina27Author Commented:
I'm not using FRS at all in my environment. I already migrated SYSVOL replication from FRS to DFSR. I'd like to stay away from ADSIedit.

Not getting any errors in event viewer. Health report says fine. When I do a Propagation report, it says "arrival pending" for Replication status from Server B to Server A.
0
 
Vince GlissonOwnerCommented:
Your PTP link, is it private?
And wether it is or it isn't, do you run a VPN thru it?
No firewalls would also include Windows firewall?
DFS uses these ports...
TCP 135, 137, 139, 389, , 445
UDP 137, 138, 389, 445
 
0
 
fina27Author Commented:
Yes it's private. We've been using it for a year without any connection issues. WIndows firewalls are off. No VPNs.

All dfsdiags come back clean as well. This is getting annoying
0
 
Vince GlissonOwnerCommented:
dfsdiag comes back clean, and still no replication to Server A.
I feel your frustration...
Have you tried to create a share with same set of files and see if it will rep to Server A with no problem.
 
0
 
fina27Author Commented:
Well the other shares work. The 3 shares that work are under 6GB. The shares that don't work are around 80GB-100GB. I think that has something to do with it.
0
 
Vince GlissonOwnerCommented:
Were there alot of files that were just added to the DFS just prior to this problem starting.
A DFS share has a limit of 5,000 links...
0
 
fina27Author Commented:
I don't know what you mean. I started off with files already in the destination location, then i set the source as primary and enabled replication. Took about two hours, and staging kept going over the watermark and having to come down again.
0
 
fina27Author Commented:
Also i beleive that 5,000 limit doesnt apply for 2008 DFS
0
 
fina27Author Commented:
I'm going to see if disabled RPC helps later tonight.
0
 
fina27Author Commented:
So around noon, none of the workstations could connect to DFS shares. It had to do with this article.....

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008100113145148?Open&seg=ent

I'm guessing that was stopping the replication too. For now, ive disabled replication and I'll redo replication configuration this weekend.
0
 
Vince GlissonOwnerCommented:
Good info fina, i'm setting up a small net soon and it will have DFS-R W2K8 and Endpoint...
Award yourself some points LOL...good troubleshoot on this one...
mesavince
0
 
fina27Author Commented:
Uninstalled Symantec fixed the issue of users not being able to connect to DFS. But I'm still experiencing 5-30 minute delays (only 1 way of replication) on one of the folders. It is the large folder... around 90GB.
0
 
Vince GlissonOwnerCommented:
90 gigs is alot to put in a dfs-r folder...
Does the entire folder replicate even tho only 1 file has changed?
Sounds like the entire folder (90GB) is replicating, when it should be doing incremental replication.
 
0
 
fina27Author Commented:
i can assure you that the entire folder is not replicating.
0
 
fina27Author Commented:
The only errors i get from DFSdiag is the following:

Validating SiteAssociation of "fileservername" in every DC.
DFSDIAG_WARNING - APPL - SiteName from IP - ::1 of "fileservername" in DC - DC02 is NULL whi
le in ADSite it is Boston,
this can lead to different referral ordering.
DFSDIAG_WARNING - APPL - SiteName from IP - ::1 of "fileservername" in DC - DC01 is NULL whi
le in ADSite it is Boston,
this can lead to different referral ordering.
DFSDIAG_WARNING - APPL - SiteName from IP - ::1 of "fileservername" in DC - DC03 is NULL wh
ile in ADSite it is Boston,
this can lead to different referral ordering.



But from googling around, it doesnt seem too severe. All i could find is to enable IPv6. Which I'll try later tonight. I've also tried unchecking RDC on the replicating folder.
0
 
fina27Author Commented:
I wish I had some clue on what is going on. I'd say about 30% of the time it works great. The other 70% of the time it takes about 30 minutes to replicate. However, if I restart the DFS Replication service on the troublesome server, it replicates immediately.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.