GetHostByName API Returns Unbindable Addresses

Article translations Article translations
Article ID: 217001
This article was previously published under Q217001
Expand all | Collapse all


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:


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.


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:
  • Windows Service Pack Center -or-

  • 152734 how to obtain the latest windows nt 4.0 service pack
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:;EN-US;CNTACTMS
This hotfix has been posted to the following Internet location as Rnr-fixi.exe (x86) and Rnr-fixa.exe (Alpha):


Microsoft 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.


Article ID: 217001 - Last Review: June 11, 2012 - Revision: 3.0
kbhotfixserver kbqfe kbbug kbfix KB217001

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from