PRB: Setting Framing Protocol (Server Type) for PhoneBook Entry

Last reviewed: August 13, 1997
Article ID: Q168441
The information in this article applies to:
  • Microsoft Windows 95 OEM Service Release version 2
  • Microsoft Windows 95
  • Microsoft Win32 Software Development Kit (SDK)

SYMPTOMS

Dial-Up Networking uses Session Management Modules (Framing Protocols) to abstract the interface presented by the dial-up server. This allows new modules and drivers to be "plugged in" as necessary to support new servers.

However, it is not possible to programmatically set the proprietary Framing Protocol for an entry in a phone-book.

CAUSE

Windows 95 has built-in support for four session management modules: PPP, RAS, Netware Connect, and SLIP. The RasSetEntryProperties() function can be used to create a new phone-book entry. But, only PPP, RAS, Netware Connect or SLIP Framing Protocols can be specified using RasSetEntryProperties() API. There are no other APIs available to accomplish this task.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Windows 95 and OEM Service Release 2 (OSR2). An update to address this problem is now available, but is not fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft does not recommend implementing this update. Contact Microsoft Technical Support for additional information about the availability of this update.


Additional query words: 95
Keywords : nt32ap kbnetwork
Version : 95
Platform : WINDOWS
Issue type : kbprb


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: August 13, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.