BUG: Winsock App Over IPX/SPX Over RAS Fails to Connect

 Last reviewed: November 29, 1995
Article ID: Q140019
The information in this article applies to:
  • Microsoft Win32 Software Development Kit (SDK) versions 3.5 and 3.51

SYMPTOMS

A Windows NT client makes a PPP (point-to-point protocol) RAS (remote access server) connection to a Windows NT RAS server with support for IPX/SPX protocols enabled. A user on a Windows NT RAS client runs a Winsock application that binds to the RAS adapter and listens for connections over SPX or SPXII protocol sequences. Another user on the Windows NT RAS server runs a Winsock application that binds to the RAS adapter on the server and tries to call connect() to connect to the application on the RAS client. A call to connect() in this scenario fails with SOCKET_ERROR and WSAGetLastError() returns WSAENETUNREACH(10051).

RESOLUTION

The RAS server administrator must configure the RAS server so that it assigns different network numbers to all RAS clients. This can be done by clearing the "Assign same network number to all IPX clients" check box. On the Control menu, click Network. Then click RemoteAccessService, click Network, and click IPX.

STATUS

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

Additional reference words: 3.50 3.51
KBCategory: kbprg kbnetwork 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: November 29, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.