IAS Does Not Log Ascend Attribute 255 Correctly

View products that this article applies to.

This article was previously published under Q195051

SYMPTOMS

The Microsoft Internet Authentication Service will log the Ascend attribute 255 (ascend-xmit-rate) in the Windows NT event log, but not in the Microsoft Internet Authentication Service log.

Back to the top

CAUSE

The Microsoft Internet Authentication Service does not interpret the Ascend attribute 255 correctly during the logging process.

Back to the top

A fix for this problem has been included on the Windows NT 4.0 Service Pack 6 (SP6) compact disc; however, it is not part of the Windows NT 4.0 SP6 standard install. This fix is located in the Support/Ias directory on the Windows NT 4.0 SP6 compact disc, and needs to be run separately.

Note: SP6 is NOT required to install this fix; it may be installed on a computer running Windows NT 4.0 SP4, SP5, or SP6. This fix should be applied after you install or reinstall any service pack. To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

http://www.microsoft.com/downloads/details.aspx?familyid=E396D059-E402-46EF-B095-A74399E25737&displaylang=en/ (http://www.microsoft.com/Windows/ServicePacks/) -or-
152734 (http://support.microsoft.com/kb/152734/EN-US/ ) how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS (http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)

Back to the top

Windows NT Server 4.0, Terminal Server Edition

To resolve this problem, obtain the latest service pack for 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

Back to the top

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.

Back to the top

MORE INFORMATION

Steps for installing the fix:

Stop the Remote Authentication Dial-In User Service (RADIUS) Service.
Replace the existing Radlog.dll with this Radlog.dll file.
Replace the existing Authserv.exe with this Authserv.exe file.
Copy _adminui.mdb and Update.exe to their own folder on the computer with the RADIUS Database.
Run update.exe. Update <dst> <src>.

Example of how to run Update.exe:

If the original _adminui.mdb is in the c:\program files\ias directory and you put the new _admin.mdb in the c:\hotfix directory, use the following command to run update.exe:

Update "c:\program files\ias\_adminui.mdb" c:\hotfix\_admin.mdb

The newly created folder is no longer needed and can be deleted along with its files Update.exe and _adminui.mdb.
Restart RADIUS.

NOTE: Do not replace the original _adminui.mdb with the new _adminui.mdb or all the customized data in the database will be lost. Update.exe syncs all the necessary information with the original _adminui.mdb and the fixed _adminui.mdb.

Back to the top