Article ID: 165989
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Server 4.0, Terminal Server Edition
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q165989
SYMPTOMS
When you run an application that uses sockets and then perform the following in this application, GetPeerName returns WSAENOTCONN.
- Issue the Connect() call in NonBlocking mode.
- Since Connect() returns asynchronously, issue the Select() call which should return when the Connect() completes.
- 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 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:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUS
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.
Additional query words: prodnt 4.00
Keywords: kbbug kbfix kbprogramming KB165989
