MS-DOS-Based RPC Application Cannot Use TCP/IP

 Last reviewed: June 15, 1995
Article ID: Q131459
The information in this article applies to:
  • Microsoft Windows Software Development Kit(SDK) for Windows, version 3.11

SUMMARY

An MS-DOS-based (16-bit) RPC application cannot use TCP/IP as the protocol sequence when running under Windows for Workgroup 3.11 with Microsoft's TCP/IP-32 driver or Windows NT's WOW layer.

MORE INFORMATION

MS-DOS-based RPC applications that use TCP/IP as the protocol sequence to communicate are designed to run only over Microsoft's real mode TCP/IP driver for Microsoft LAN Manager client software for MS-DOS or any other compatible real-mode TCP/IP driver implementation.

Windows for Workgroup's TCP/IP-32 protocol driver and Windows NT's WOW layer do not provide the same real-mode interface for TCP/IP as provided by the Microsoft LAN Manager TCP/IP driver.

When an MS-DOS-based RPC application tries to use TCP/IP as the protocol sequence under Windows for Workgroups with Microsoft's TCP/IP-32 driver or Windows NT's WOW layer, RPC run time report exception 27(0x1b).

Additional reference words: LanManager
KBCategory: kbprg kbnetwork
KBSubCategory: NtwkRpc

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: June 15, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.