Windows Server 2012 Failover Clustering and Remote procedure call failed (800706BE)

Question

When i want to validate cluster configuration i get this error message: The Remote procedure call failed.(Exception from HRESULT:0X800706be)

I disabled the Firewall and Anti-Virus but the problem still exists. RPC Service is running and all ports like 135 are open. In windows server 2012 Remote Registry service start up is Automatic (Trigger Start), I started that service manually but nothing changed.

Solution

The problem was related to network card configuration. I disabled "Large Send Offload V2(IPv4)" and "Large Send Offload V2(IPv6)" on my network card and the problem solved.

Comments

[fukawi2]

Include examples of the commands you are running

[the-wabbit]

You should check if the clock on all cluster members, the domain controller and your management station is synchronized. Unsynchronized clocks can cause authentication failures and lead to misleading error messages from the cluster service.

[Yazdkhasti]

Time of these servers is synchronized to domain controller.The problem is related to accessing admin shares but i dont know what is the reason.

[Yazdkhasti]

I use physical hardware but as you said the problem is related to accessing admin shares like c$. I checked DNS on these servers and it's working fine.I can access admin shares on these servers from other computers but not from eachother.

[Tonny]

@Yazdkhasti Weird. On physical hardware this should work out of the box... Maybe our in-house cluster guru has some ideas, but he won't be in the office until Monday next week. I'll ask him then and update here if he comes up with something sensible.

[Yazdkhasti]

I reinstalled Windows on both servers and the problem solved.

[Tonny]

@Yazdkhasti Glad to hear you got it working. But not very satisfying not knowing what was the root-cause... Anyway, sometimes that's just the way it is.

[Yazdkhasti]

I created the cluster and the cluster was working until today. I get the same error when i run validate cluster wizard. It fails at network configuration check.