GetPeerName() Returns WSAENOTCONN After Select() Returns Success

• Microsoft Windows NT Workstation version 4.0
• Microsoft Windows NT Server version 4.0

SYMPTOMS

When you run an application that uses sockets and then perform the following in this application, GetPeerName returns WSAENOTCONN.

1. Issue the Connect() call in NonBlocking mode.

2. Since Connect() returns asynchronously, issue the Select() call which should return when the Connect() completes.

3. After the Select() returns, issue the GetPeerName() call which retrieves the name of the peer to which a socket is connected.

CAUSE

A timing problem allows Select(); to return before Connect();.

RESOLUTION

To resolve this problem, put a Sleep(0) after the Select() function call; or apply the hotfix mentioned in this article.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was corrected in the latest Microsoft Windows NT 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K