ROB Posted December 13, 2013 Posted December 13, 2013 Hi We are having a problem enabling replication on our VMs. we have two hyper visors each running 2012r2. The Hyper-V manager is being run from win8.1 If i set up a vm on hyper-A then try to enable replication to hyper-B i get the following error: hyper-v failed to enable replication for virtual machine. The server name or address could not be resolved (0x00002EE7) If I set up a vm on hyper-B and try to enable replication to hyper-A it works fine. I can ping both servers from each other I have tied the "fix" suggested here Does any one else have a suggestion to try? Rob
ROB Posted December 16, 2013 Author Posted December 16, 2013 Thanks for replying. No neither Hyper-V machine are in a cluster.
gjefferies Posted December 16, 2013 Posted December 16, 2013 Can Hyper-vA ping Hyper-vB? Firewall ports open Are you using http or https? Thanks Gareth
ROB Posted December 16, 2013 Author Posted December 16, 2013 Yes Hyper-A can ping Hyper-B. I have opened the firewall ports, for testing I have turned off the firewall as well. Using http - kerberos Thanks
gjefferies Posted December 16, 2013 Posted December 16, 2013 Ok Cool, Have you tried adding the servers to the hosts file? Have you delegated the server in kerberos? Any other events being logged in eventvwr? Cheers Gareth
ROB Posted December 16, 2013 Author Posted December 16, 2013 Hi thanks, I have delegated the server in kerberos (AD users and computers) There are no untoward events being logged. I just tried adding the servers to their local hosts file (I had not done this before) and it appears to make no difference. Rob
gjefferies Posted December 16, 2013 Posted December 16, 2013 Have you tried turning off Replication on the Hyper-V host and enabling it again? Cheers Gareth
ROB Posted December 16, 2013 Author Posted December 16, 2013 Hi yes have tried this no joy im afraid. Rob
gjefferies Posted December 16, 2013 Posted December 16, 2013 Ok I out of ideas... Log a call with Microsoft I guess
kevin_lane Posted December 16, 2013 Posted December 16, 2013 What does the event logs say dont forget 2012 r2 is still new and might need to wait for patches
ROB Posted February 18, 2014 Author Posted February 18, 2014 Success... It appears that the NIC drivers for my HP Proliant had an update that would only work using server 2012 not 2012r2 when applied replication works as it should do to another 2012 server. I have discovered that replication can not go from a 2012r2 host to a 2012 host but will work the other way round (OK unless you want to failover) I have also discovered that you can not migrate vms from a 2012r2 host to a 2012 host. If the os of your vm is linux based then you can create a new vm on a 2012 host and attach the vhdx however if it is a windows os then this will not work. So I have now downgraded my servers both to 2012 updated the drivers on my HP (the other is a Dell) . I have also rebuilt all my vms (they are using 2012r2). see also spiceworks and technet Thanks for all your suggestions. Rob
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now