Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts. View solution. View Solution. Why EE? Courses Ask. Get Access. Log In. Web Dev. We help IT Professionals succeed at work. Last Modified: We are trying to configure Hyper-V R2 replication in our environment.
Both source and destination are clustered 2 hosts each cluster. We have configured the replica broker role on both servers and chose http replication on ports want to avoid certificate dependencies 3. Both environments are on the same domain but on different sites connected via MPLS no firewalls in the middle 4.
Telnet works to the destination server and port Issue is when we try to enable replication for a VM, it fails with error Hyper-V failed to establish a connection with Replica server Error Code 0xEFE. Start Free Trial. View Solution Only. Commented: Your error says port ?Experts Exchange always has the answer, or at the least points me in the correct direction!
Subscribe to RSS
It is like having another employee that is extremely experienced. Being involved with EE helped me to grow personally and professionally. We've partnered with two important charities to provide clean water and computer science education to those who need it most.
Connect with Certified Experts to gain insight and support on specific technology challenges including:. Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.
View solution. View Solution.
Why EE? Courses Ask. Get Access.
Log In. Web Dev. We help IT Professionals succeed at work. Hyper-V Replica failing. Last Modified: Error message appears at the end when attempting to finish the configuration: Hyper-V failed to enable replication. Hyper-V failed to establish a connection with the Replica server.
No logs showing any connection on the Destination Replica. This servers are on different domains and different sites. There is no trust relationship. So I assumed I needed to use certificate based authentication to make it work. Configured proper ports on our ASA on the destination servers' side for I also completely opened it on the local Windows firewall and in our ASA for troubleshooting. Am I missing something here? I've seen a couple forums where people are having the same issue but either no resolution on it or the solution did not resolve it for me.
Start Free Trial. View Solutions Only.Primary server at Site A. Replica Server at Site B. I set up all my virtual servers on the primary server, enabled Replica.
Replication was occurring normally.Hyper-V Replica Broker Replication Error
I wanted to test failing over a virtual machine, so i did a planned failover from site A to site B, which went smoothly except that reversing the replication direction failed. So, after the failover, i went to manually reverse the replication direction from B back to A, but it would not work. So, I removed replication, and deleted any files left from the particular VM remaining on site A.
Now i am attempting to enable replication from B to A and cannot get it to work. I recieve the error in the subject line. The two servers communicate over a site to site VPN, and replication from site A to site B is currently working fine for the other servers.
It seems like the connection is being refused immediately, but i cannot figure out why. Any help would be greatly appreciated here. I can answer any questions that might be helpful. Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff microsoft. Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question.
Quick access. Search related threads. Remove From My Forums. Asked by:.
Advanced Troubleshooting of Hyper-V Replica – Part 1
Archived Forums. Sign in to vote. Hi, I am having a problem enabling replication on one of my Virtual Machines. My setup is this: Primary server at Site A. Thank you!! Monday, June 8, PM.
Anyone have any ideas? Tuesday, June 9, AM. Best Regards, Elton Ji Please remember to mark the replies as answers if they help and unmark them if they provide no help. Thursday, June 11, AM.Troubleshooting issues with the Hyper-V Replica requires extensive knowledge of the technology.
Not only you need to have knowledge but you must also be able to follow a troubleshooting approach which helps you fix the issues and also benefits in finding the root cause. Before you start reading the first part of this article series, please familiarize yourself with the Hyper-V Replica technology by reading a few Hyper-V Replica articles published on this blog.
You must also know how to perform a Hyper-V replication health check. I have written a series of articles on this topic, which can be found here:. You can encounter a number of issues with the Hyper-V Replica. For example, a virtual machine might fail to replicate its contents to Replica Server due to the network connectivity. Similarity, replication might not occur if a firewall or a network device is blocking the required network ports.
This article explains what you should do if a particular condition occurs. Both Primary and Replica Server might not communicate because of authentication issues. Test-VMReplicationConnection offers a few parameters which you can use to perform other checks but if you need to quickly test the connection between a Primary and a Replica Server then execute the below command or as it is shown in the below screenshot:.
Local over network port 80 using the Kerberos authentication protocol which is Active Directory-based authentication mechanism for Hyper-V Replica. The same error is reported in the Event Viewer also. Your first task is to fix the connection issue between Primary and Replica Server, if any! To fix the connection issues, you can think of the following possibilities and then move ahead to troubleshoot the issue further:.
Replica Server or Primary Server cannot communicate with Active Directory or the trust relationship for these two computer accounts has been broken. You need to run this command on both Primary and Replica Servers individually and make sure the output reported is similar to as shown in the below command window:. Replica Server or Primary Server is not authorized to access each other over the network.
Please note both Primary and Replica Servers communicate over the network. They might fail to communicate if a Group Policy setting has been applied which prevents the network communication. The Group Policy Setting should contain the computer accounts of Primary and Replica Servers or at least make sure to add Authenticated Users security group which contains both computer accounts. In case of the name resolution issues, an event will be generated in the Event Viewer as shown in the below screenshot:.
You can actually use Ping and NSLookup commands to test the connectivity and name resolution. It is imperative to understand that it is Primary Server which needs to resolve the name of the Replica Server to an IP Address if replication is one way e. From Primary to Replica Server. Replica Server might hit with the name resolution issue only if reverse replication action is used. Replica Server is not listening on the required network ports. Replica Server must listen on the required network ports.Both machines are on the same domain, but are in different physical locations connected over a site-to-site VPN.
When I click finish, I keep getting the following:. This is over port The firewall is off on both hosts. Not trying to do anything with a certificate. When I try and do a replica to another machine on the same subnet, it doesn't work either Just says 'Hyper-V failed to enable replication'.
Hyper-V 2012 R2 replication error Code 0x00002EFE
This issue is almost always related to firewall blocking. In fact, just create an IP to IP rule between hosts. Additionally, on the local "Microsoft" or other firewall, make sure the same rules exist for the domain profile.
While troubleshooting you might consider adding the rules for all profiles. Everything is open. I can dig into the logs and see what is going on. It flows just fine. To continue this discussion, please ask a new question.
Get answers from your peers along with millions of IT pros who visit Spiceworks. When I click finish, I keep getting the following: This is over port What am I missing here? Popular Topics in Virtualization. Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need. Verify your account to enable IT peers to see that you are a professional. Virtualization expert.
ElRoasto This person is a verified professional. Or just use the commands given above to see if the traffic is flowing properly. This topic has been locked by an administrator and is no longer open for commenting. Read these nextVirtual Machine is giving me this error.
It is not my first error from Virtual Machine but could manage them and I could continue the processes. It seems like I cannot solve this one and please is there any online expert that can help me with this one?
Error: The connection with the server was terminated abnormally 0xEFE. It is also possible that Kerberos is having a hard time communicating over the VPN in case you are using a slow virtual private network link.
Because many VPN routers are set to drop or release fragmented packets which cause Kerberos to fail the authentication, you need to make sure that your router is configured to allow fragmented packets over the virtual private network tunnel and set Kerberos to utilize TCP instead of UDP as the default transmission protocol.
Every router will be different depending on the model and brand. After this restart your server. You must apply this method of modifying the registry on both the target and source Hyper-V servers and you should permit fragmented packet handling on both ends of the tunnel. Hyper-V failed to enable replication. Hi, Virtual Machine is giving me this error.
Enable Replication Enabling replication failed. Hyper-V failed to authenticate using Kerberos authentication. About Sharath Reddy. Questions 1. Answers Best Answers Vote Up 0 Vote Down. Access violation at address B6F0 in module Samsung. Windows could not apply unattended settings during pass offlineServicing Next. Related Questions. Problem when installing Labview solution By.
However this doesn't make sense as I can ping the server ping works from both sides and I can connect to port 80 and from each side VS1 and VS2 - note they are on different subnets however that shouldn't matter.
Also both servers are part of the domain so authentication shouldn't be an issue I am logged in as a domain admin and have a valid kerberos ticket and there is nothing in any of the event logs that gives me any sort of clue as to what is wrong. I was able to solve it by enabling BypassProxyServer. Learn more. Asked 1 year, 11 months ago. Active 1 year, 7 months ago. Viewed 2k times. The current error is: [Main Instruction] Enabling replication failed.
Anyone have any ideas of what might be wrong? Shawn Shawn 1 1 silver badge 13 13 bronze badges. Active Oldest Votes. AzureBaum AzureBaum 61 7 7 bronze badges.
Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog.
Podcast Ben answers his first question on Stack Overflow. The Overflow Bugs vs.