Computer with Disjoined Namespace Is Not Authenticated by Using 802.1x with a Radius Server in its Domain

Article translations Article translations
Article ID: 330030 - View products that this article applies to.
This article was previously published under Q330030
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page

SYMPTOMS

A computer with a disjoined namespace is not authenticated with a RADIUS server in the computer's domain by using 802.1x.

A computer with a disjoined namespace is a computer whose DNS domain name differs from the Active Directory domain DNS name.

CAUSE

A computer that is in a disjoined-namespace configuration is not authenticated correctly when the computer tries to access the wireless access point. Although both the computer and the user in the domain have obtained certificates, the following error is logged on the server when the computer tries authentication with the domain controller (the RADIUS server). In this environment (EAP/TLS authentication), the EAP/TLS negotiation does not succeed with the following statement (according to the Rastls.log file):
[1080] 14:56:32:828: QuerySecurityContextToken failed and returned 0x8009030b
"0x8009030b" means "SEC_E_NO_IMPERSONATION: The security context does not allow impersonation of the client." This message is the "visible" part of the authentication problem; the error code is not very straightforward.

RESOLUTION

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix 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
   --------------------------------------------------------
   01-Nov-2002  11:11  5.0.2195.6109  124,688  Adsldp.dll
   01-Nov-2002  11:11  5.0.2195.5781  131,344  Adsldpc.dll
   01-Nov-2002  11:11  5.0.2195.6109   62,736  Adsmsext.dll
   01-Nov-2002  11:11  5.0.2195.6052  358,160  Advapi32.dll
   01-Nov-2002  11:11  5.0.2195.6094   49,936  Browser.dll
   01-Nov-2002  11:11  5.0.2195.6012  135,952  Dnsapi.dll
   01-Nov-2002  11:11  5.0.2195.6076   96,016  Dnsrslvr.dll
   01-Nov-2002  11:11  5.0.2195.5722   45,328  Eventlog.dll
   01-Nov-2002  11:11  5.0.2195.6059  146,704  Kdcsvc.dll
   01-Nov-2002  10:52  5.0.2195.6112  204,048  Kerberos.dll
   21-Aug-2002  08:27  5.0.2195.6023   71,248  Ksecdd.sys
   23-Oct-2002  12:45  5.0.2195.6101  507,664  Lsasrv.dll
   23-Oct-2002  12:45  5.0.2195.6101   33,552  Lsass.exe
   27-Aug-2002  14:53  5.0.2195.6034  108,816  Msv1_0.dll
   01-Nov-2002  11:11  5.0.2195.5979  307,472  Netapi32.dll
   01-Nov-2002  11:11  5.0.2195.6075  360,720  Netlogon.dll
   01-Nov-2002  11:11  5.0.2195.6100  920,848  Ntdsa.dll
   01-Nov-2002  11:11  5.0.2195.6100  389,392  Samsrv.dll
   01-Nov-2002  11:11  5.0.2195.6100  130,320  Scecli.dll
   01-Nov-2002  11:11  5.0.2195.6100  303,376  Scesrv.dll
   23-Oct-2002  12:45  5.1.2195.0     146,704  Schannel.dll
   01-Nov-2002  11:11  5.0.2195.5859   48,912  W32time.dll
   04-Jun-2002  13:32  5.0.2195.5859   57,104  W32tm.exe
   01-Nov-2002  11:11  5.0.2195.6100  126,224  Wldap32.dll
				

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 Microsoft Windows 2000 Service Pack 4.

MORE INFORMATION


For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173 The Datacenter Program and Windows 2000 Datacenter Server Product

Properties

Article ID: 330030 - Last Review: February 27, 2014 - Revision: 1.10
APPLIES TO
  • Microsoft Windows 2000 Professional SP1
  • Microsoft Windows 2000 Professional SP2
  • Microsoft Windows 2000 Service Pack 3
  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Server SP2
  • Microsoft Windows 2000 Service Pack 3
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Advanced Server SP2
  • Microsoft Windows 2000 Advanced Server SP3
Keywords: 
kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbwin2ksp4fix kbbug kbfix kbwin2000presp4fix KB330030

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com