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



The information in this article applies to:

  • Microsoft Windows 95
  • Microsoft Platform Software Development Kit (SDK) 1.0

This article was previously published under Q168441

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.

RESOLUTION

This issue is resolved by the following updated files for Windows 95 and OSR2, and later versions of these files:
   RNASMM.DLL  version 4.40.311   dated 4/1/97  4,608 bytes
   RNASMM.LIB  (no version info)  dated 4/1/97  3,472 bytes
   RNASMM.H    (no version info)  dated 4/1/97  1,074 bytes
				


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 computers experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft does not recommend implementing this update at this time. Contact Microsoft Technical Support for additional information about the availability of this update.

This issue is resolved in Microsoft Windows 98.

For additional information about Windows 95 updates, please see the following article in the Microsoft Knowledge Base:

161020 Implementing Windows 95 Updates


Modification Type:MinorLast Reviewed:7/11/2005
Keywords:kbAPI kbnetwork kbprb KB168441