POP3 and IMAP Clients Are Not Authenticated on Exchange Server 2000 (272492)



The information in this article applies to:

  • Microsoft Windows NT Server 4.0
  • Microsoft Windows NT Server 4.0 SP6a
  • Microsoft Windows NT Server, Enterprise Edition 4.0
  • Microsoft Windows NT Server, Enterprise Edition 4.0 SP6a
  • Microsoft Windows NT Workstation 4.0
  • Microsoft Windows NT Workstation 4.0 SP6a
  • Microsoft Exchange 2000 Server

This article was previously published under Q272492

SYMPTOMS

When the Exchange Server 2000 registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA has the LmCompatibilitylevel value set to 5, POP3 and IMAP clients are not authenticated.

CAUSE

This issue occurs because the 5 value does not allow a check for clear text passwords, and authentication therefore does not work properly.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix should have the following file attributes or later:
   Date         Time   Size     File name     Platform
   ---------------------------------------------------
   25-Sep-2000  21:07  247,056  Advapi32.dll  x86
   25-Sep-2000  21:08   48,400  Msv1_0.dll    x86

   25-Sep-2000  21:06  403,728  Advapi32.dll  Alpha
   25-Sep-2000  21:06   79,632  Msv1_0.dll    Alpha
				

STATUS

Microsoft has confirmed that this is a problem in Windows NT 4.0.

Modification Type:MinorLast Reviewed:9/2/2005
Keywords:kbbug kbfix kbQFE KB272492