GetHostByName API Returns Unbindable Addresses (217001)
The information in this article applies to:
- Microsoft Windows NT Server 4.0 SP4
- Microsoft Windows NT Server, Enterprise Edition 4.0 SP4
- Microsoft Windows NT Workstation 4.0 SP4
This article was previously published under Q217001 SYMPTOMS
After you apply Windows NT 4.0 Service Pack 4, Windows Sockets applications
using the "bind()" function with IP address information retrieved using "GetHostByName()" to return localhost IP addresses may fail and return the following error message:
10049 (WSAEADDRNOTAVAIL)
CAUSE
A change was introduced in Service Pack 4 that causes NDISWAN Services to return IP addresses in the order in which they are bound. This change resulted in IP addresses not currently bound to the TCP/IP stack to be returned when making a call to the Winsock API function GetHostbyName(). Sockets applications using the "bind()" function for individual addresses returned from "GetHostByName()" on systems running the RAS (Remote Access Server) Service may experience this problem.
RESOLUTION
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or
the individual software update. For information on obtaining the
latest service pack, please go to:
For information on obtaining the individual software update, contact Microsoft
Product Support Services. For a complete list of Microsoft Product Support
Services phone numbers and information on support costs, please go to the
following address on the World Wide Web:
This hotfix has been posted to the following Internet location as Rnr-fixi.exe (x86) and Rnr-fixa.exe (Alpha): STATUSMicrosoft has confirmed that this is a problem in Windows NT 4.0 Service Pack 4. This problem was first corrected in Windows NT version 4.0 Service Pack 5.
| Modification Type: | Minor | Last Reviewed: | 9/23/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbfix kbQFE KB217001 |
|---|
|