BUG: Windows 95-Based Winsock App Can't Receive IPX Broadacast

Last reviewed: January 30, 1996
Article ID: Q137914

The information in this article applies to:

Microsoft Win32 Software Development Kit (SDK) version 4.0

SYMPTOMS

A winsock application is unable to receive IPX broadcasts when running under Windows 95 even though it is able to receive UDP broadcasts.

RESOLUTION

To enable a winsock application to recieve IPX broadcasts, use the setsockopt() call with the SO_BROADCAST flag as in this example:

   int sock, optval;
   .
   .
   sock = socket(.....);
   err = setsockopt( sock, SOL_SOCKET, SO_BROADCAST, (char*)&optval,
         sizeof(optval));

STATUS

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

MORE INFORMATION

Note that there is no need to use this option for the case of UDP and specification for winsock 1.1 says that this is needed only for sending broadcasts.

Additional reference words: 4.00 Windows 95
KBCategory: kbnetwork kbtshoot kbbuglist
KBSubcategory: NtwkWinsock

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: January 30, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.