Article ID: 931855 - Last Review: December 1, 2007 - Revision: 1.2 Authentication fails when you configure a Windows XP-based computer to use IEEE 802.1X authentication to connect to a networkSYMPTOMSWhen you configure a Microsoft Windows XP-based computer to use IEEE 802.1X authentication to connect to a network, the authentication fails. CAUSEThis problem occurs when the computer name contains a double-byte character or a hyphen (-). 802.1X uses the Extensible Authentication Protocol (EAP) for message exchange during the authentication process. The Windows implementation of the Extensible Authentication Protocol (EAP) does not support these characters. WORKAROUNDTo work around this problem, change the name of the computer to use single-byte characters without hyphens.
MORE INFORMATIONWhen this problem occurs, an error that resembles the following is logged in the EAP log: [1244] 20:12:06:422: ElGetUserIdentity entered [1244] 20:12:06:422: ElGetEapUserInfo: Get value succeeded: EapTypeId=<25>, SSIDLen=<32>, AuthData=(610) [1244] 20:12:06:422: ElGetEapUserInfo: Get value succeeded: EapTypeId=<25>, SSIDLen=<32>, AuthData=(610) [1244] 20:12:06:422: ElGetUserIdentityOptimized: ElGetEapUserInfo: Got user blob, size = (610) [1244] 20:12:06:422: ElGetCustomAuthData: SSIDLen=<32>, EapTypeId=<25>, Offset=<52/180>, dwAuthData=<62> [1244] 20:12:06:422: ElGetCustomAuthData: SSIDLen=<32>, EapTypeId=<25>, Offset=<52/180>, dwAuthData=<62> [1244] 20:12:06:422: ElGetUserIdentityOptimized: WideCharToMultiByte (가나다\bb40480) failed: 122 [1244] 20:12:06:422: ElGetUserIdentity: ElGetUserIdentityOptimized got identity without user module intervention [1244] 20:12:06:422: ElGetUserIdentity completed with error 122 APPLIES TO
| Article Translations
|
Back to the top
