BUG: Winsock 2 Issue when Not Using the FD_CONNECT Notification

ID: Q199434

The information in this article applies to:

Microsoft Win32 Software Development Kit (SDK)
on the following platforms: Win95, Win98

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 : kbnetwork kbAPI kbSDKPlatform kbWinOS95 kbWinOS98bug kbWinsock kbGrpNet
Version : WINDOWS:
Platform : WINDOWS
Issue type : kbbug