Hyper-V Replication Fails Between Standalone Windows Server 2022 Hosts

Anonymous
2024-12-09T14:37:40+00:00

I am trying to set up Hyper-V replication between two standalone Windows Server 2022 hosts (not part of an Active Directory domain). Despite following the required steps, I am encountering an error when enabling replication.

The error states:

Enabling replication failed.
Hyper-V failed to enable replication.

Hyper-V was unable to establish a connection with the replica server.

Hyper-V failed to enable replication for virtual machine 'Debian 12': %%12030 (0x00002EFE). (Virtual machine ID E1E8D0E6-A683-4968-8E98-419E2258CDE1)

Hyper-V could not establish a connection to replica server 'WIN-17VPVFVOKGO.local' on port '80'. Error: %%12030 (0x00002EFE).

Note: Enabled the firewall rule: Hyper-V Replica HTTP Listener (TCP-In) on both servers.

Setup Details:

  1. Primary Server: Server02
  2. Replica Server: Server09
  3. Virtual Machine: Debian12
  4. Authentication: Kerberos (HTTP) on port 80
  5. Environment:
    • Both servers are physically co-located and standalone (not AD members).
      • Firewalls on both servers have the rule "Hyper-V Replica HTTP Listener (TCP-In)" enabled for port 80.
        • Replication is configured to allow connections from any authenticated server.

Steps Followed:

  1. Installed the Hyper-V role on both servers.
  2. Enabled "Allow this computer to act as a Replica Server" in Hyper-V settings on both host
  3. Primary Server: Serve1
  4. Replica Server: Server02
  5. Selected Use Kerberos (HTTP) and set the port to 80 under the authentication and port settings.
  6. Enabled the firewall rule: Hyper-V Replica HTTP Listener (TCP-In) on both servers.
  7. Attempted to enable replication from the primary host for a specific virtual machine
  8. System defaulting to port 443 when HTTP (port 80) is explicitly selected.
  9. Continuted with Use Kerberos authentication (HTTP) (port 443) is explicitly selected.
           [![](https://filestore.community.support.microsoft.com/api/images/c404d007-f683-4385-a6ca-72acc93b1860?upload=true&fud_access=hC1SxZhn7m%2FZQJkOIiOVstu10yTQgXS4A%2FDBzZTg8nbaCgIogkrcDydMeI5Y4za2dOqDdWtsG2JNS3E35V60i9TiGHR7STMpJHheeXuDvO8nwjUlqCBHhJ0NDvuYN7OSHRlSYFV8VpjuyP2M5q%2FfUMfBWGGuKLJNFh24Tj2FVdR85wXKVYtjdf1Z0Qy3s2fLC50a16%2FIN%2FQuZw23MS1qZca7a7ItTcKC0wnY%2FQNuFWr2scALpj1AfPhmYHcfJcGoeZaDa6xPwL47TVArF6JdZmS%2Fl6HWliqhCIGZWZC9dh99zcm%2FE6i4yx1LL6RfdPPl%2FqEQf%2B0qBpxVHfKfDbRo4U94Q4ZIVReqldqkuh5sqKiZUd%2BUawbjIFLZXT2Tnakp1ZsPmSAC%2BoOp8TXulo%2Bh0Km4TdDpzWzEeQZSK0YVYT4%3D)](https://filestore.community.support.microsoft.com/api/images/c404d007-f683-4385-a6ca-72acc93b1860?upload=true&fud_access=hC1SxZhn7m%2FZQJkOIiOVstu10yTQgXS4A%2FDBzZTg8nbaCgIogkrcDydMeI5Y4za2dOqDdWtsG2JNS3E35V60i9TiGHR7STMpJHheeXuDvO8nwjUlqCBHhJ0NDvuYN7OSHRlSYFV8VpjuyP2M5q%2FfUMfBWGGuKLJNFh24Tj2FVdR85wXKVYtjdf1Z0Qy3s2fLC50a16%2FIN%2FQuZw23MS1qZca7a7ItTcKC0wnY%2FQNuFWr2scALpj1AfPhmYHcfJcGoeZaDa6xPwL47TVArF6JdZmS%2Fl6HWliqhCIGZWZC9dh99zcm%2FE6i4yx1LL6RfdPPl%2FqEQf%2B0qBpxVHfKfDbRo4U94Q4ZIVReqldqkuh5sqKiZUd%2BUawbjIFLZXT2Tnakp1ZsPmSAC%2BoOp8TXulo%2Bh0Km4TdDpzWzEeQZSK0YVYT4%3D "filestore.community.support.microsoft.com")
    
             [![](https://filestore.community.support.microsoft.com/api/images/38ffd08d-b2af-46ce-92a3-6c8bc04b230d?upload=true&fud_access=hC1SxZhn7m%2FZQJkOIiOVstu10yTQgXS4A%2FDBzZTg8nbaCgIogkrcDydMeI5Y4za2dOqDdWtsG2JNS3E35V60i9TiGHR7STMpJHheeXuDvO8nwjUlqCBHhJ0NDvuYN7OSHRlSYFV8VpjuyP2M5q%2FfUMfBWGGuKLJNFh24Tj2FVdR85wXKVYtjdf1Z0Qy3s2fLC50a16%2FIN%2FQuZw23MS1qZca7a7ItTcKC0wnY%2FQNuFWqKpZ4x5%2BHoNdjKilZjMSbeGDaA1UWoZ5CDr%2F%2FwXZX9kGq4iZnPKb6R6OVW4QSAMcOZcxVhbqn2otHKHjeR9TSChGavebFE4c5EX0IMJvpJ%2FF%2FamzdMNx%2BziuKdh71%2BYsorBvZ4obPFDQiUWJpOC7GW2PaQ8y0SdZsJTTJKFo57OOzBf8KOzjCyJ4u6gb5iePo%3D)](https://filestore.community.support.microsoft.com/api/images/38ffd08d-b2af-46ce-92a3-6c8bc04b230d?upload=true&fud_access=hC1SxZhn7m%2FZQJkOIiOVstu10yTQgXS4A%2FDBzZTg8nbaCgIogkrcDydMeI5Y4za2dOqDdWtsG2JNS3E35V60i9TiGHR7STMpJHheeXuDvO8nwjUlqCBHhJ0NDvuYN7OSHRlSYFV8VpjuyP2M5q%2FfUMfBWGGuKLJNFh24Tj2FVdR85wXKVYtjdf1Z0Qy3s2fLC50a16%2FIN%2FQuZw23MS1qZca7a7ItTcKC0wnY%2FQNuFWqKpZ4x5%2BHoNdjKilZjMSbeGDaA1UWoZ5CDr%2F%2FwXZX9kGq4iZnPKb6R6OVW4QSAMcOZcxVhbqn2otHKHjeR9TSChGavebFE4c5EX0IMJvpJ%2FF%2FamzdMNx%2BziuKdh71%2BYsorBvZ4obPFDQiUWJpOC7GW2PaQ8y0SdZsJTTJKFo57OOzBf8KOzjCyJ4u6gb5iePo%3D "filestore.community.support.microsoft.com")
    
       **10. Error:**  
    
         `☑ Enabling replication failed.`
    
         `Hyper-V failed to enable replication.`
    
         `Hyper-V cannot connect to the replica server. `
    
         `Hyper-V failed to enable replication for the virtual machine 'Debian12_Network_Installation': %%12002 (0x00002EE2).    `
    

(Virtual machine ID B1FE98FA-95EA-4CF7-AADB-1D60D587B3A4)

        `Hyper-V cannot connect to the specified replica server 'WIN-HG604ASL06L.local'. Error: %%12002 (0x00002EE2). Verify that the specified server is enabled as a replica server, accepts incoming connections on port '443', and supports the same authentication scheme.`

Error Observed: When configuring the connection parameters for replication, the default port is set to 443 (which is for HTTPS).

I manually updated it to 80 (as we are using HTTP). However, enabling replication fails with the attached error message (screenshot).

          [![](https://filestore.community.support.microsoft.com/api/images/5a7fba2e-1276-4da5-bf63-cac848f3232b?upload=true&fud_access=hC1SxZhn7m%2FZQJkOIiOVstu10yTQgXS4A%2FDBzZTg8nbaCgIogkrcDydMeI5Y4za2dOqDdWtsG2JNS3E35V60i9TiGHR7STMpJHheeXuDvO8nwjUlqCBHhJ0NDvuYN7OSHRlSYFV8VpjuyP2M5q%2FfUMfBWGGuKLJNFh24Tj2FVdR85wXKVYtjdf1Z0Qy3s2fLC50a16%2FIN%2FQuZw23MS1qZca7a7ItTcKC0wnY%2FQNuFWpKwN6V1gZXViUyJjIcwUVtO5LTYsFIdd7DUBaEfoS6gHTy1bNmv6Q9wh3vKgnFUZ3udeSvpsUbIAinO5T304Q%2F1BzkyJeGQASJMz3jgR1SKxg3qKnOR2Hy9QP1F12fos%2BvexIcyu4CDKTJpVmvQZOUjXSN%2FntUg1nj64vyPDTECM%2Fv5dfy6zQrThpt8oTFciQ%3D)](https://filestore.community.support.microsoft.com/api/images/5a7fba2e-1276-4da5-bf63-cac848f3232b?upload=true&fud_access=hC1SxZhn7m%2FZQJkOIiOVstu10yTQgXS4A%2FDBzZTg8nbaCgIogkrcDydMeI5Y4za2dOqDdWtsG2JNS3E35V60i9TiGHR7STMpJHheeXuDvO8nwjUlqCBHhJ0NDvuYN7OSHRlSYFV8VpjuyP2M5q%2FfUMfBWGGuKLJNFh24Tj2FVdR85wXKVYtjdf1Z0Qy3s2fLC50a16%2FIN%2FQuZw23MS1qZca7a7ItTcKC0wnY%2FQNuFWpKwN6V1gZXViUyJjIcwUVtO5LTYsFIdd7DUBaEfoS6gHTy1bNmv6Q9wh3vKgnFUZ3udeSvpsUbIAinO5T304Q%2F1BzkyJeGQASJMz3jgR1SKxg3qKnOR2Hy9QP1F12fos%2BvexIcyu4CDKTJpVmvQZOUjXSN%2FntUg1nj64vyPDTECM%2Fv5dfy6zQrThpt8oTFciQ%3D "filestore.community.support.microsoft.com")

          [![](https://filestore.community.support.microsoft.com/api/images/af43e609-e357-41ba-b070-9369b5229c32?upload=true&fud_access=hC1SxZhn7m%2FZQJkOIiOVstu10yTQgXS4A%2FDBzZTg8nbaCgIogkrcDydMeI5Y4za2dOqDdWtsG2JNS3E35V60i9TiGHR7STMpJHheeXuDvO8nwjUlqCBHhJ0NDvuYN7OSHRlSYFV8VpjuyP2M5q%2FfUMfBWGGuKLJNFh24Tj2FVdR85wXKVYtjdf1Z0Qy3s2fLC50a16%2FIN%2FQuZw23MS1qZca7a7ItTcKC0wnY%2FQNuFWqdWUomURu80KbmJ3KFny3ri4oS0JW2sYL04ocmjdiqOOI4K3IHB0hlotSJvNzGfNwv8kAgQfjnWzgCBktyDktSQlncHJZ7azABkPhr5lhUSwZu2heVfKW6M8b5b0t4zLhMJ3K2SzZaofaiB%2Btwc9WbpwY%2BThIzFMcz2kB%2F5g3U77Vj6xQa45Y01Z%2B7z8n5vGg%3D)](https://filestore.community.support.microsoft.com/api/images/af43e609-e357-41ba-b070-9369b5229c32?upload=true&fud_access=hC1SxZhn7m%2FZQJkOIiOVstu10yTQgXS4A%2FDBzZTg8nbaCgIogkrcDydMeI5Y4za2dOqDdWtsG2JNS3E35V60i9TiGHR7STMpJHheeXuDvO8nwjUlqCBHhJ0NDvuYN7OSHRlSYFV8VpjuyP2M5q%2FfUMfBWGGuKLJNFh24Tj2FVdR85wXKVYtjdf1Z0Qy3s2fLC50a16%2FIN%2FQuZw23MS1qZca7a7ItTcKC0wnY%2FQNuFWqdWUomURu80KbmJ3KFny3ri4oS0JW2sYL04ocmjdiqOOI4K3IHB0hlotSJvNzGfNwv8kAgQfjnWzgCBktyDktSQlncHJZ7azABkPhr5lhUSwZu2heVfKW6M8b5b0t4zLhMJ3K2SzZaofaiB%2Btwc9WbpwY%2BThIzFMcz2kB%2F5g3U77Vj6xQa45Y01Z%2B7z8n5vGg%3D "filestore.community.support.microsoft.com")

Questions:

  1. Why is the system defaulting to port 443 when HTTP (port 80) is explicitly selected?
  2. Is there a specific configuration required for Kerberos authentication between standalone servers?
Windows Server High availability Virtualization and Hyper-V

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Anonymous
    2024-12-10T02:52:48+00:00

    Hi,

    The replica server port field does not change automatically. You have to modify it manually when you change the authentication type.

    If you want to use Kerberos in Hyper-V replication, a Kerberos Key Distribution Center (KDC) is required for authentication, which is integrated in a domain controller by default. Since your Hyper-V hosts are standalone servers, you can use certificate-based authentication (HTTPS). Or it's needed to set up a KDC yourself. You may check to see if there are third party solutions for that.

    1 person found this answer helpful.
    0 comments No comments