Logon Requests May Not Work with Certain Third-Party Authentication Providers (298905)



The information in this article applies to:

  • Microsoft Windows 2000 Server SP1
  • Microsoft Windows 2000 Server SP2
  • Microsoft Windows 2000 Advanced Server SP1
  • Microsoft Windows 2000 Advanced Server SP2
  • Microsoft Windows 2000 Professional SP1
  • Microsoft Windows 2000 Professional SP2

This article was previously published under Q298905

SYMPTOMS

If certain third-party authentication providers are installed on the client and a domain logon occurs, the LogonUser or LsaLogonUser function may return STATUS_NETLOGON_NOT_STARTED instead of STATUS_DLL_NOT_FOUND. This problem is known to occur with Citrix UNIX Integration Services.

CAUSE

If the authentication provider is not installed on the domain controllers and is installed only on the client, under some circumstances, the authentication provider cannot distinguish between the dynamic-link library (DLL) not being found and the Netlogon service not being started.

RESOLUTION

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

260910 How to Obtain the Latest Windows 2000 Service Pack

The English version of this fix should have the following file attributes or later:
   Date        Time    Version        Size     File name
   --------------------------------------------------------
   16-Nov-2001  09:54  5.0.2195.4600  123,664  Adsldp.dll
   16-Nov-2001  09:54  5.0.2195.4628  130,320  Adsldpc.dll
   16-Nov-2001  09:54  5.0.2195.4016   62,736  Adsmsext.dll
   16-Nov-2001  09:54  5.0.2195.4622  356,112  Advapi32.dll
   16-Nov-2001  09:54  5.0.2195.4571   82,704  Cmnquery.dll
   16-Nov-2001  09:54  5.0.2195.4141  133,904  Dnsapi.dll
   16-Nov-2001  09:54  5.0.2195.4379   91,408  Dnsrslvr.dll
   16-Nov-2001  09:54  5.0.2195.4534   41,744  Dsfolder.dll
   16-Nov-2001  09:54  5.0.2195.4534  156,944  Dsquery.dll
   16-Nov-2001  09:54  5.0.2195.4574  110,352  Dsuiext.dll
   16-Nov-2001  09:55  5.0.2195.4607  521,488  Instlsa5.dll
   16-Nov-2001  09:54  5.0.2195.4630  145,680  Kdcsvc.dll
   05-Nov-2001  11:02  5.0.2195.4592  199,440  Kerberos.dll
   04-Sep-2001  08:32  5.0.2195.4276   71,024  Ksecdd.sys
   07-Nov-2001  11:57  5.0.2195.4607  503,568  Lsasrv.dll
   07-Nov-2001  11:57  5.0.2195.4607   33,552  Lsass.exe
   16-Nov-2001  09:46  5.0.2195.4648  107,280  Msv1_0.dll
   16-Nov-2001  09:54  5.0.2195.4594  306,960  Netapi32.dll
   16-Nov-2001  09:54  5.0.2195.4603  358,672  Netlogon.dll
   16-Nov-2001  09:54  5.0.2195.4635  912,656  Ntdsa.dll
   16-Nov-2001  09:54  5.0.2195.4627  387,856  Samsrv.dll
   16-Nov-2001  09:54  5.0.2195.4583  128,784  Scecli.dll
   16-Nov-2001  09:54  5.0.2195.4600  299,792  Scesrv.dll
   16-Nov-2001  09:54  5.0.2195.4600   48,400  W32time.dll
   06-Nov-2001  11:43  5.0.2195.4600   56,592  W32tm.exe
   16-Nov-2001  09:54  5.0.2195.4600  125,712  Wldap32.dll
   07-Nov-2001  11:57  5.0.2195.4607  503,568  Lsasrv.dll
				

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 Windows 2000 Service Pack 3.

MORE INFORMATION

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:

249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes


Modification Type:MinorLast Reviewed:9/26/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbSecurity kbWin2000PreSP3Fix kbWin2000sp3fix KB298905