Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

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.

↑ Back to the top


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

↑ Back to the top


Status

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

↑ Back to the top


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

↑ Back to the top


Keywords: kbqfe, kbfix, kbsurveynew, kbexpertiseadvanced, kb

↑ Back to the top

Article Info
Article ID : 2984325
Revision : 1
Created on : 1/7/2017
Published on : 11/3/2014
Exists online : False
Views : 289