Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Error message on a Windows Server 2003-based computer or on a Windows Server 2008-based computer when you log on to an iSCSI target by using CHAP authentication: "Authentication Failure"


View products that this article applies to.

Beta Information
This article discusses a beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this beta product. For information about how to obtain support for a beta release, see the documentation that is included with the beta product files, or check the Web location where you downloaded the release.
Beta Information
This article discusses a beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this beta product. For information about how to obtain support for a beta release, see the documentation that is included with the beta product files, or check the Web location where you downloaded the release.

↑ Back to the top


Symptoms

Consider the following scenario:
You use the Microsoft iSCSI Software Initiator on a Windows Server 2003-based computer or on a Windows Server 2008-based compute to connect to an iSCSI target.
You use CHAP authentication.
On the iSCSI target, you configure the CHAP username or the shared secret to contain non-ASCII characters.
You enter the correct user name or the shared secret, and you try to log on to the target.
In this scenario, you receive the following error message:
Authentication Failure

↑ Back to the top


Cause

This problem occurs because Microsoft iSCSI Software Initiator uses the active code page to encode CHAP credentials. For example, if you have Japanese characters in the CHAP user name or in the shared secret, the Japanese characters are encoded as Shift-JIS instead of as the standard UTF-8.

↑ Back to the top


Workaround

To work around this problem, use only ASCII characters in the CHAP user name and the shared secret.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


Keywords: kberrmsg, kbtshoot, kbprb, KB946482

↑ Back to the top

Article Info
Article ID : 946482
Revision : 3
Created on : 1/6/2008
Published on : 1/6/2008
Exists online : False
Views : 296