Article ID: 162230 - Last Review: November 1, 2006 - Revision: 2.2 Fragmentation and Performance Issues with PPTP ConnectionsThis article was previously published under Q162230 IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restoring the Registry" Help topic in Regedit.exe or the "Restoring a Registry Key" Help topic in Regedt32.exe. On This PageSYMPTOMS
Performance degradation may occur when you use Point-to-Point Tunneling
Protocol (PPTP) connections.
RESOLUTIONTo resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
152734
(http://support.microsoft.com/kb/152734/EN-US/
)
How to Obtain the Latest Windows NT 4.0 Service Pack
This hotfix does the following:
NOTE: Ndiswan.sys is the 40-bit version and Ndiswand.sys is the 128-bit version of this file. If you are using 128-bit encryption, you will need to install Ndiswand.sys and rename it to Ndiswan.sys to retain your encryption. After you apply the fix, shut down and restart your computer. WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it. Registry ChangeThe registry change below can be used to increase performance on a reliable network. If the network is unreliable or congested, this setting should be set to the default value; otherwise, set this value to 8.NOTE: This registry change is not a requirement for the hotfix itself, but should be used to gain performance under reliable conditions.
STATUSMicrosoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4. | Article Translations
|
Back to the top
