Article ID: 946482
Article Last Modified on 1/6/2008
APPLIES TO
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Windows Server 2008 Datacenter
- Windows Server 2008 Datacenter 32-Bit
- Windows Server 2008 Enterprise
- Windows Server 2008 Enterprise 32-Bit
- Windows Server 2008 for Itanium-Based Systems
- Windows Server 2008 Standard
- Windows Server 2008 Standard 32-Bit
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.
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:
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.
WORKAROUND
To work around this problem, use only ASCII characters in the CHAP user name and the shared secret.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Keywords: kberrmsg kbtshoot kbprb KB946482
