Microsoft DFS not replicating

I have a DFS share setup with replication between 6 servers. I am noticing that replication is not working properly. Replication was working until i upgraded 4 of the server from 2008r2 to 2012. I will attach the diagnostic report for your to view. If you need more information feel free to ask. I appreciate your help in advance.
Health-dfs-files-16Oct2013-2050.html
jww77Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

TMekeelCommented:
Looks like a DNS issue.  Why all the fe80:: IPv6 addresses?
0
jww77Author Commented:
We use Microsoft Direct Access which requires IPv6. Can you be more specific please?
0
TMekeelCommented:
fe80 is link-local.
That will not resolve well.  Stop DNS from listening on IPv6 and see if that helps.
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

TMekeelCommented:
Or better, utilize IPv6, via DHCP or static addressing and set AAAA records for your servers if IPv6 is necessary.
0
jww77Author Commented:
ok, I think the second option would work. I need DNS to listen on IPv6 since DA works with IPv6 I will work on that and give and update.
0
jww77Author Commented:
I tried setting up IPv6 and it did not fix the problem. I opened a support ticket with Microsoft and they were able to help me resolve the issue. They had me run this command

wmic /namespace:\\root\microsoftdfs path dfsrVolumeConfig whe
re volumeGuid="A04BB231-8909-11E2-87AC-0002A54EAC2E" call ResumeReplication

I had already ran the command before I called Microsoft, but it only partially fixed the problem. The support guy then explained that the Guid is specific to the volume that is being replicated, and that the command will need to be ran on every server and volume that is having the issue. In the event viewer I found that the replication errors display the Guid that is having the problem. In the command I replaced the Guid with the one I found in the event viewer and ran it on every server that was having issues. Moments later replication was back up and working properly. Keep in mind that some of my servers have multiply drives that are being replicated, and in those cases there are multiple Guids. You might have to run the command multiple times, each time with a different Guid.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
TMekeelCommented:
Thanks for posting the resolution, glad you got it sorted!
0
jww77Author Commented:
I accepted my own as solution because it is what fixed the problem.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.