Microsoft KB Archive/159573
Article ID: 159573
Article Last Modified on 11/1/2006
- Microsoft Windows NT Server 3.51
- Microsoft Routing and Remote Access Service Update for Windows NT Server 4.0
This article was previously published under Q159573
This article contains a copy of the Routing and Remote Access Upgrade for Microsoft Windows NT 4.0 Server Hotfix Update 1.0 Release Notes. Routing and Remote Access Upgrade for Microsoft Windows NT 4.0 Server Hotfix Update 1.0 is available at:
NOTE: Because the Microsoft Web site is regularly updated, the site address may change without notice. If this occurs, link to the Microsoft home page at the following address:
Please use this document to address questions which may arise during the installation of this hotfix for the Routing and Remote Access Upgrade for Microsoft Windows NT 4.0 Server.
1.0 Information On Installing This Update
This hotfix requires that you already have the Routing and Remote Access Service Upgrade for Windows NT 4.0 Server installed on your system. There are no other requirements to install this hotfix. The Routing and Remote Access Service Upgrade can be found at:
This hotfix is packaged in an auto-install format. Double-click the executable name or type the executable name at a command prompt to install it. For this hotfix, type rrasfixi.exe for x86 platforms or rrasfixa.exe for Alpha platforms.
The files can also be extracted from the hotfix without installing them. To do this, copy the hotfix to a temporary directory, and type rrasfixi /x or rrasfixa /x at a command prompt. After extracting the files, the hotfix can be installed by typing hotfix at a command prompt.
The files that are replaced on your computer when you install this hotfix are copied into a directory called $NtUninstallQ159573$ under your Windows NT 4.0 install directory.
The symbol files are available in the downloadable files named "rrassymi.exe" for x86 platforms or "rrassyma.exe" for Alpha platforms (without the quotation marks).
2.0 New Features Added In This Update
2.1 Allowing PPP clients to connect without authentication
Setting this registry key:
to (DWORD) 3 allows the server to accept incoming PPP clients without authentication.
2.2 Using MS-CHAP with Remote Authentication Dial-In User Service (RADIUS) authentication
In order to enable MS-CHAP with RADIUS authentication, you must add a registry value of:
and set it to (DWORD) 1. Once this is enabled every incoming PPP connection will be offered MS-CHAP, and MS-CHAP will be used to authenticate each PPP user against the RADIUS server that your RAS server is using.
3.0 List Of Issues Fixed In This Update
All bug fixes contained in this hotfix are listed below. You can query the Microsoft Knowledge Base to find an article about a specific bug by using the Q
xxxxxx number that is assigned to the bug. The Microsoft Knowledge Base can be found on the Microsoft Web site at:
172290 Routing and Remote Access "Out of Buffers" Event Logs
176689 RRAS Requires hotfix when Using Proxy 2.0
173533 WinNT Radius Client Sends Incomplete Accounting Information
176506 Radius Accounting Only Logs One Entry for Multilink Client
173532 Radius Authentication Causes Access Violation in Mprouter.exe
172512 Routing and Remote Access Event ID 20100
176502 RAS Authentication Rechallenge Resets Compression Flag
176209 RAS or RRAS Server Fails to Answer Incoming Calls
167038 RAS Clients Run Winsock and RPC Applications Slowly
171061 RIP Does Not Advertise Zero Subnets
160517 RRAS May Decrement Local Static Route Metric
176082 RRAS Server Updates Link State Database but not Route Table
162834 RRAS Stops Routing After Encountering Zero Checksum
104296 RRAS Uses Larger MTU Than Other OSPF Routers
Additional query words: read-me service pack sp servpack
Keywords: kbreadme KB159573