Article ID: 214555 - Last Review: November 1, 2006 - Revision: 1.5 RADIUS Server Fails to Authenticate Users in a Remote DomainThis article was previously published under Q214555 SYMPTOMS
Microsoft Internet Authentication Server (RADIUS) can be used to authenticate remote dial-in users from another domain if the Radius server's domain trusts the user's domain. To successfully authenticate users from a domain other than the RADIUS server's domain, the user name supplied should be in the form of domain\user and the Radius server's domain should trust the user's domain. However, when you dial into a Routing and Remote Access server that is using a Radius server for authentication, cross-domain authentication may fail even when you specify the user name in the domain\user format. RESOLUTION
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://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS
(http://support.microsoft.com/default.aspx?scid=fh;en-us;cntactms)
STATUSMicrosoft has confirmed that this is a problem in Microsoft Routing and Remote Access Service Update for Windows NT Server 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5. MORE INFORMATION
When installing the hotfix using Service Pack or hotfix.exe or hfx.exe the following registry entries are added automatically. But, if applying the fix manually then the following registry changes need to be done manually:
| Article Translations
|
Back to the top
