RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft Windows 2000 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the
Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name
--------------------------------------------------------
11-Sep-2003 17:12 5.0.2195.6738 417,552 Oakley.dll
11-Sep-2003 17:12 5.0.2195.6800 58,128 Rasman.dll
11-Sep-2003 17:12 5.0.2195.6817 153,872 Rasmans.dll
11-Sep-2003 17:12 5.0.2195.6738 54,032 Rastapi.dll
WORKAROUND
To work around the problem without installing the hotfix, you must correct the remote access/Telephony API (TAPI) configuration. To do this, use the Netset.exe tool to add the Layer 2 Tunneling Protocol (L2TP) and the Point-to-Point Tunneling Protocol (PPTP).
For additional information about the Netset.exe tool, click the following article number to view the article in the Microsoft Knowledge Base:
268781
Description of the Netset.exe Tool from the Windows 2000 Resource Kit
The typical Netset.exe answer file that includes L2TP and PPTP might look similar to the following code. Notice that the L2TP and PPTP entries are listed under Protocols and Parameters.
[UserData]
ComputerName=ComputerName
[Networking]
InstallDefaultComponents=Yes
[NetAdapters]
Adapter1=params.Adapter1
[params.Adapter1]
INFID=*
[NetClients]
MS_MSClient=params.MS_MSClient
[NetServices]
MS_SERVER=params.MS_SERVER
[NetProtocols]
MS_PPTP=params.MS_PPTP
MS_L2TP=params.MS_L2TP
MS_TCPIP=params.MS_TCPIP
[params.MS_PPTP]
[params.MS_L2TP]
[params.MS_MSClient]
[params.MS_TCPIP]
AdapterSections=params.MS_TCPIP.Adapter1
[params.MS_TCPIP.Adapter1]
SpecificTo=Adapter1
DHCP=No
IPAddress=<IP address>
DefaultGateway=<Default Gateway IP>
SubnetMask=<Subnet Mask IP>
DNSServerSearchOrder=<DNS IP1>, <DNS IP2>
WINS=Yes
WINSServerList=<WINS1>,<WINS2>
NetBIOSOptions=1