Article ID: 193059 - View products that this article applies to.
This article was previously published under Q193059
The IP Helper API (IPHLPAPI) is a public API that provides Windows network configuration and statistics information to Windows 32-bit applications. The API is available for Windows NT 4.0 Service Pack 4 and later, and for Windows 98 and Windows 2000. Not all IP Helper APIs are available for Windows NT 4.0 and Windows 98 platforms.
This article provides a brief description of the IP Helper APIs available, grouped by the task they perform or the object they operate on. Additional information for the IP Helper APIs, including sample code, will be available on the Windows NT 5.0 Beta 2 Platform SDK release and later.
Interface ClassThis class allows applications to retrieve network adapter characteristic information. The IP Helper APIs available for Windows NT 4.0 Service Pack 4 are listed below:
IP Address ClassThis class allows applications to modify and retrieve IP configuration information. However, most of these APIs are not supported on Windows NT 4.0 Service Pack 4. The IP Helper APIs available for Windows NT 4.0 SP 4 are listed below:
ARP Table ClassThis class provides access to the address resolution protocol (ARP) entries by mapping from an IP address to a physical address. The IP Helper APIs available for Windows NT 4.0 Service Pack 4 are listed below:
Route Table ClassThis class allows applications to retrieve IP routing information and permits applications to make modifications to route entries in the table. Routing is the selection of the next hop address from a routing table over which a packet is sent. The IP Helper APIs available for Windows NT 4.0 Service Pack 4 are listed below:
Statistics ClassThis class provides information on various kinds of packet/connection statistics information on a local computer. The IP Helper APIs available for Windows NT 4.0 Service Pack 4 are listed below:
IP Helper API ConventionsInterfaces are addressed by index, which is a large DWORD number. For applications that expect friendly interface numbers (for example, MIB, UI), use GetFriendlyIndex() for one-way conversion into friendly index.
Functions that return an array of structures take in/out size parameter pSize. The user initializes pSize so it points to the size of the buffer passed to the function. After a successful call, this parameter holds the actual size of the data returned. If the function fails because the buffer is too small, pSize points to the buffer size required to hold all available data and the function returns a Win32 error status. Most of these IP Helper APIs return ERROR_INSUFFICIENT_BUFFER; the exception is that the GetNetworkParams() and GetAdaptersInfo() APIs return ERROR_BUFFER_OVERFLOW.
Article ID: 193059 - Last Review: July 11, 2005 - Revision: 2.4