Microsoft KB Archive/192582

From BetaArchive Wiki
Knowledge Base


XCLN: Cannot Log On to Exchange with NT Account Containing Extended Characters

Article ID: 192582

Article Last Modified on 10/28/2006



APPLIES TO

  • Microsoft Outlook 97 Standard Edition, when used with:
    • Microsoft Windows NT 4.0
    • Microsoft Windows 98 Standard Edition
    • Microsoft Windows 95
  • Microsoft Outlook 98 Standard Edition, when used with:
    • Microsoft Windows NT 4.0
    • Microsoft Windows 98 Standard Edition
    • Microsoft Windows 95
  • Microsoft Exchange Server 5.5 Standard Edition



This article was previously published under Q192582


SYMPTOMS

When a user does one of the following:

  • Logs on to Exchange with an account from a Windows NT domain that is not trusted by the Windows NT domain of the Exchange Server computer.


-OR-

  • Uses the "Use Network Security during Logon" option.

The user is prompted to enter credentials for the target domain.

If the user name contains an extended character (ASCII over 127), such as the character ñ (Alt 0241), the user cannot log on. The correct credentials are rejected with the following error message:

The logon credentials supplied were incorrect. Make sure your username
and domain are correct, then type your password again.



WORKAROUND

To work around this problem, do not use the "Use Network Security during Logon" option, and have the users and the Exchange Server computer in the same Windows NT domain.

RESOLUTION

To resolve this problem, obtain the latest service pack for Exchange Server version 5.5. For more information, please see the following article in the Microsoft Knowledge Base:

191014 XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack



The English version of this fix should have the following file attributes or later:

Component: Outlook


   File Name      Version
   -------------------------
   Emsabp32.dll   5.5.2392.0
   Emsmdb32.dll   5.5.2392.0
   Emsui32.dll    5.5.2392.0
   Mspst32.dll    5.5.2392.0
                

STATUS

Microsoft has confirmed this to be a problem in the Microsoft Outlook clients listed at the beginning of this article.

Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe KB192582