GetPeerName() Returns WSAENOTCONN After Select() Returns Success

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.

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

To work around this problem, put a Sleep(0) after the Select() function call.

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.