BUG: Winsock 2 Issue when Not Using the FD_CONNECT Notification (199434)


The information in this article applies to:

  • Microsoft Platform Software Development Kit (SDK) 1.0, when used with:
    • the operating system: Microsoft Windows 95
    • the operating system: Microsoft Windows 98
This article was previously published under Q199434

SYMPTOMS

If a Winsock 2 application connects to a peer application and then only sets FD_WRITE in the lNetworkEvents bitmask when calling WSAEventSelect(), but does not also set FD_CONNECT, then the application will hang in WSAWaitForMultipleEvents() after the socket gets connected.

RESOLUTION

A simple workaround solution to this is to simply set FD_CONNECT in the lNetworkEvents bitmask when calling WSAEventSelect, even if a connection has already been established using connect or WSAConnect.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.
Modification Type:MinorLast Reviewed:7/11/2005
Keywords:kbDSWNET2003Swept kbAPI kbBug kbnetwork kbWinsock KB199434
©2004 Microsoft Corporation. All rights reserved.