TCP connection fails and triggers a "WSAEACCES" error on a virtual interface in Windows Server 2012 R2

Applies to: Windows Server 2012 R2 DatacenterWindows Server 2012 R2 StandardWindows Server 2012 R2 Essentials

Symptoms


Consider the following scenario:

  • You create a Windows Server 2012 R2-based one-node cluster.
  • You try to add a node in Add Node Wizard in Failover Cluster Manager on the cluster.
  • The wizard window freezes while displaying a "Waiting for notification that node nodename is a fully functional member of the cluster" message, and it times out eventually.
In this scenario, the Transmission Control Protocol (TCP) connection on the virtual interface fails, and you receive the "WSAEACCES" error message.

Resolution


To resolve this issue, install update rollup 2984006. For more information about how to obtain this update rollup package, click the following article number to view the article in the Microsoft Knowledge Base:

2984006 September 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates