Share via

Replication (SYSVOL) EventID's 4612 and 5012

Bill C 21 Reputation points
2021-12-31T15:22:45.257+00:00

I have 2 Server 2019 Domain controllers. AD01 and AD02. AD01 has all FSMO roles.

Have been in the process of eliminating 2 Server 2012 DC's

In Event ID 5012, Error 9026 on AD01 I see the following

//////////////////////////////

The DFS Replication service failed to communicate with partner AD01 for replication group Domain System Volume. The partner did not recognize the connection or the replication group configuration.

Partner DNS Address: AD01.domain.org

Optional data if available:
Partner WINS Address: AD01
Partner IP Address: ::1

/////////////////////////////////

I believe that the ip address being shown is incorrect and that it should be 10.5.5.4.

It seems like that the incorrect " Partner IP Address: ::1 " is IPV6 related. So while I mention that, I do want to say that IPV6 has been disabled. I don't understand how or where " ::1 " is being picked up from.

AD02 DFS Replication logs look clean without errors.

In DNS and was resolving the correct IP address 10.5.5.4 along with with the " ::1 " address and saw this and didn't think anything of this. After i started to see EVENT ID 5012 with the " ::1 " addressing for AD01, I when back through DNS and eliminated all the " ::1 " instances leaving just 10.5.5.4 for AD01. The hope was that " Partner IP Address: ::1 " would change to Partner IP Address: 10.5.5.4

Does anyone have any ideas where " ::1 " is coming from?

Windows for business | Windows Server | User experience | Other
0 comments
Accepted answer
  1. Anonymous
    2021-12-31T16:32:00.95+00:00

    You could also try a non authoritative sync
    https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo

    or simply demote, reboot, promo again the problematic one.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

7 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-12-31T15:31:48.51+00:00

    Does anyone have any ideas where " ::1 " is coming from?

    IPv6 loopback address

    I'd check that each domain controller has own static ip address plus loopback (127.0.0.1) listed for DNS and no others such as router or public DNS. Its also very important to verify domain health is 100% before adding new ones into the mix.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

  2. Bill C 21 Reputation points
    2021-12-31T16:08:10.213+00:00

    @Anonymous

    This happened after removing the old Server 2012 instance. DFS Replication was working fine prior to the removal.

    So I verified the IPV4 IP address and loopback 127.0.0.1 as you suggested.

    How do I stop the IPv6 loopback address? IPv6 is not enabled on these DC's

    161636-image.png

  3. Bill C 21 Reputation points
    2021-12-31T20:25:38.153+00:00

    @Anonymous
    I tried the non-authoritative sync as you suggested. That did not resolve the replication problem.

    161667-bad-sync-error-5012-1.jpg

    0 comments
  4. Anonymous
    2021-12-31T20:30:49.587+00:00

    Another simple resolution may be to move roles off, demote, reboot, promo it again. While it is demoted it wouldn't hurt to confirm domain health was 100% before next steps.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.