Microsoft KB Archive/285927

From BetaArchive Wiki
Knowledge Base


Outlook 2000 Does Not Support the UPN Logon Method Outside of a Windows 2000 Domain

Article ID: 285927

Article Last Modified on 9/23/2005



APPLIES TO

  • Microsoft Outlook 2000 Standard Edition, when used with:
    • Microsoft Windows 2000 Standard Edition



This article was previously published under Q285927

SYMPTOMS

When you use a Microsoft Exchange 2000 server with Outlook 2000 in a Windows 2000 domain, the user principle name (UPN) logon method works correctly. However, if the Microsoft Windows 2000-based client computer is not a part of the Windows 2000 domain that the Exchange 2000 server is located in, the UPN log on attempt may not work and you may receive a prompt to supply the user name, domain, and password.

RESOLUTION

To resolve this problem, obtain the latest service pack for Microsoft Office 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

276367 OFF2000: How to Obtain the Latest Office 2000 Service Pack


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

   Date      Time      Version      Size    File name     
   -----------------------------------------------------
1/31/2000   7:26:56 PM 9.0.0.3731   196661  Oladd.fae    
4/5/2000    1:02:20 PM 9.0.0.4005   192561  Mimedir.dll
5/22/2000   5:35:14 PM n/a          170617  Olxchng9.chm
5/23/2000   9:20:06 AM n/a          150690  Olexchng.aw
5/23/2000   5:19:26 AM n/a           554068  Outlhlp.aw_0001
5/30/2000  12:53:14 PM n/a            26643  Olsec9.chm
6/2/2000    4:45:52 AM 9.0.0.4201    86067  Envelope.dll
6/2/2000    5:30:30 AM 9.0.0.4201    65586  Sendto9.dll
6/14/2000  11:11:40 AM 1.0.3.27 41472  Bjablr32.dll
6/14/2000  11:12:12 AM 3.2.0.27 61952  Bjlog32.dll
6/14/2000  11:14:54 AM 1.0.3.27     183808  Emablt32.dll
6/19/2000  12:12:12 PM 5.5.2652.65  808720  Cdo.dll_0004
6/19/2000  12:49:48 PM 5.5.2652.65  716560  Cdo.dll
7/7/2000   12:41:30 PM 9.0.0.4307    73772  Rm.dll
7/7/2000    9:03:32 AM 5.5.3138.0   528656  Mspst32.dll_0005
7/7/2000    9:07:18 AM 5.5.3138.0   602384  Mspst32.dll_0004
8/31/2000   1:43:04 AM 5.5.3142.0   154112  Emsabp32.dll_0005
11/16/2000  2:25:02 AM 9.0.0.4715   122931  Contab32.dll_0002
11/21/2000  3:05:00 AM n/a           129024  Out2ksec.mst
1/8/2001    3:37:14 AM 1.0.3.28  98304  Bjsrch32.dll
1/31/2001   8:48:47 AM 8.30.3152.0  782608  Outex.dll
2/8/2001   11:17:59 AM 5.5.3153.0   454144  Omi9.dll_0001
2/8/2001   11:21:39 AM 5.5.3153.0   548352  Omint.dll_0001
4/6/2001    5:18:36 AM 9.0.0.5205  1675315  Outllibr.dll
5/9/2001   11:35:24 AM 5.5.3156.0   540944  Exsec32.dll_0005
5/21/2001  12:16:34 PM 5.5.3157.0   623104  Msmapi32.dll_0002
5/21/2001  12:20:28 PM 5.5.3157.0   792576  Msmapi32.dll_0001
5/25/2001   8:50:20 AM 9.0.5324.0   368691  Pstprx32.dll_0002
5/25/2001   8:56:09 AM 5.5.3158.0   594192  Emsmdb32.dll_0005
6/1/2001    6:54:06 AM 9.0.0.5331  5328946  Outllib.dll
6/1/2001    7:15:00 AM 5.5.3159.0   131344  Emsui32.dll_0005
                



STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Office 2000 Service Pack 3 (SP-3).


Additional query words: OL2K

Keywords: kbhotfixserver kbqfe kboffice2000sp3fix kbfix kbbug KB285927