Knowledge Base

BUG: Winsock 2 Issue when Not Using the FD_CONNECT Notification

Article ID: 199434

Article Last Modified on 7/11/2005

Microsoft Platform Software Development Kit-January 2000 Edition, when used with:
- Microsoft Windows 95
- Microsoft Windows 98 Standard Edition

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.

Additional query words: kbDSupport

Keywords: kbbug kbwinsock kbapi kbnetwork kbdswnet2003swept KB199434