I set up Hyper-V replication between two servers (Server 2012 Standard, and Hyper-V Server 2012) on the same subnet. Using Kerberos authentication on port 80, replication worked perfectly on site. I then moved one server offsite (different AD site with different subnet) that is connected by a site-to-site VPN. Hyper-V Replication is only working in one direction. In the opposite direction, I keep getting this error:

Enabling Replication Failed. Hyper-V failed to enable replication for virtual machine 'MACHINENAME': The connection with the server was terminated abnormally (0x00002EFE).

I havent had much luck searching on this error.

-No bad entries in DNS
-Domain Controllers with DNS are available in each site.
-Sites and Services, and their subnets are set up correctly
-No Routing problems, both sites can talk to each other, each server can ping each other by name
-The windows server firewalls are off
-Remote desktop and remote management are working from server to server.
-The VPN should not be blocking any ports or services, AFAIK.
-Port scanning shows 80 and 135 are open on each side.

I'm making my site-to-site VPN with Cisco hardware to Sonicwall hardware. Anything I should look for in my VPN config? Ports? Any help is appreciated.

• Edited by EdMVP Wednesday, October 31, 2012 1:23 AM

Hiya,

Curious question, is the route the same from site A to B, as it is from B to A?

The VPN does the routing, and the VPN is made from our gateways. We didn't have to add any other routes, and there aren't any sites in between.

Unless you have black fiber between your sites, your using the internet. If your using the internet, your using routes. The VPN "just" encapsulates your communication.

The quick test is to use tracert from host A target host B and visa versa and confirm the routes are identical.

Here's my TracerRts, from server to server, and back.

Site A (192.168.0.0/24) has a switch in between the server and the gateway. The switch is 192.168.0.1. Site A machines have their default gateway set to the switch, and a route has been added to the switch for the gateway.

Site B (10.0.0.0/24), the server is connected directly to the gateway.

From Site A, machine 1:

C:\>tracert MACHINE2-SITEB

Tracing route to MACHINE2-SITEB.domain.com [10.0.0.4]

over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.0.1

  2    19 ms    22 ms    27 ms  MACHINE2-SITEB.domain.com [10.0.0.4]

Trace complete.

From site B, machine 2:

C:\>tracert MACHINE1-SITEA

Tracing route to MACHINE1-SITEA.domain.com [192.168.0.12]

over a maximum of 30 hops:

  1    35 ms    19 ms    18 ms  MACHINE1-SITEA.domain.com [192.168.0.12]

  2    23 ms    18 ms    33 ms  MACHINE1-SITEA.domain.com [192.168.0.12]

Trace complete.

Hi,

General Methodology for troubleshooting Hyper-V Replica connectivity issues between Primary and Replica servers:

1. Verify the Replica server is booted and running.
2. Check network connectivity and name resolution functionality between the Primary and Replica server by executing ping and nslookup tests.  If ping test fails, resolve network connectivity issues.  If name resolution fails, check DNS
3. Ensure the Replica server is listening on the Replica Server Port.  This can be accomplished by running a netstat -ano command on the Replica server after verifying the  appropriate firewall rule has been Enabled or the custom firewall rule has been configured to allow Inbound communications on the configured port
   
4. Inspect the System Event Log on the Primary and Replica servers to determine if there is any failure condition associated with network functionality
5. Run the Hyper-V Best Practice Analyzer (BPA) and inspect the report for any configuration or operational issues

For more information please refer to this article for further troubleshooting:

Understand and Troubleshoot Hyper-V Replica
http://www.microsoft.com/en-us/download/details.aspx?id=29016

For more information please refer to following MS articles:

Hyper-V Replica Overview
http://technet.microsoft.com/en-us/library/jj134172.aspx
Demonstrate Planned Failover in Hyper-V Replica
http://technet.microsoft.com/en-us/library/hh831759.aspx

Hope this helps!

TechNet Subscriber Support

If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here

It turns out, a third party internet management and monitoring device (Cymphonix) was the culprit. It's in use at Site A, and it's somehow interfering with the
replication traffic.

I've been through the "Understand and Troubleshoot Guide Hyper-V Replica in Windows Server 8 Beta .docx" document and found it marginally helpful. Replication worked onsite, VPN traffic was flowing, DNS was correct, Ping worked, nslookup and and netstat -ano output looked correct.

• Marked as answer by EdMVP Friday, November 02, 2012 7:52 PM
• Edited by EdMVP Friday, November 02, 2012 7:53 PM

I just had this exact same issue.  After reading this we checked all around our network and found someone had put Spiceworks desktop on one of the servers to 'monitor' things.  Replication started working after I turned it off.  We're only at 75% after 12 hours, but we had 4 days worth of replications to do.

Hi, 

I'm having this exact issue right now. Would you be able to offer any other ideas? Site A, like yours, has a switch between it and the gateway. Site B, directly connected to the gateway. Site to site VPN connecting the sites....set up replication with both servers at Site A, moved one to site B, and now replication only works from A to B. I've been looking everywhere trying to figure this out...hope you can help!!