BUG: getsockopt for IPX_MAX_ADAPTER_NUM Fails on Windows 95

Last reviewed: November 14, 1995
Article ID: Q139131

The information in this article applies to:

Microsoft Win32 Software Development Kit (SDK) version 4.0

SYMPTOMS

When an application calls getsockopt with option IPX_MAX_ADAPTER_NUM on Windows 95, the call fails with Winsock error 10042 (Bad Protocol Option).

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are reasearching this bug and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

The following article in the Microsoft Knowledge Base illustrates a way to use getsockopt() and IPX_MAX_ADAPTER_NUM to enumerate addresses for Winsock families other than IP. This example works in Windows NT, but because of the problem documented in this article, it will not work in Windows 95

   ARTICLE-ID: Q129315
   TITLE     : How to Use WinSock to Enumerate Addresses

Additional reference words: 4.00 Windows 95
KBCategory: kbnetwork kbbuglist
KBSubcategory: NtwkMisc

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: November 14, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.