Article ID: 320711 - View products that this article applies to.
This article was previously published under Q320711
You may not be able to bind to Lightweight Directory Access Protocol (LDAP) by using the Sun Java Naming and Directory Interface (JNDI) library against a Windows 2000-based Active Directory server.
Active Directory cannot handle handshake data and application data in the same packet. Depending on the timing and the underlying networking code, the final phase of the (reuse session) negotiation handshake might cause handshake data and application data to be placed in the same packet. This condition causes the bind call on the client not to work.
Service Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/260910/EN-US/ )How to Obtain the Latest Windows 2000 Service Pack
Hotfix InformationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix should have the following file attributes or later:
NOTE: Apply this fix to the Active Directory server, not the client.
Date Time Version Size File name -------------------------------------------------------- 03-Apr-2002 02:37 5.0.2195.4959 123,664 Adsldp.dll 30-Jan-2002 02:52 5.0.2195.4851 130,832 Adsldpc.dll 30-Jan-2002 02:52 5.0.2195.4016 62,736 Adsmsext.dll 03-Apr-2002 02:37 5.0.2195.5201 356,624 Advapi32.dll 03-Apr-2002 02:37 5.0.2195.4985 135,952 Dnsapi.dll 03-Apr-2002 02:37 5.0.2195.4985 95,504 Dnsrslvr.dll 03-Apr-2002 02:37 5.0.2195.5246 145,680 Kdcsvc.dll 23-Mar-2002 01:50 5.0.2195.5246 199,952 Kerberos.dll 07-Feb-2002 21:35 5.0.2195.4914 71,024 Ksecdd.sys 02-Mar-2002 23:32 5.0.2195.5013 503,568 Lsasrv.dll 02-Mar-2002 23:32 5.0.2195.5013 33,552 Lsass.exe 08-Dec-2001 02:05 5.0.2195.4745 107,280 Msv1_0.dll 03-Apr-2002 02:37 5.0.2195.4917 306,960 Netapi32.dll 03-Apr-2002 02:37 5.0.2195.4979 360,208 Netlogon.dll 03-Apr-2002 02:37 5.0.2195.5523 917,264 Ntdsa.dll 03-Apr-2002 02:37 5.0.2195.5201 386,832 Samsrv.dll 30-Jan-2002 02:52 5.0.2195.4874 128,784 Scecli.dll 03-Apr-2002 02:37 5.0.2195.5258 299,792 Scesrv.dll 03-Apr-2002 02:37 5.0.2195.5259 48,400 W32time.dll 27-Mar-2002 08:06 5.0.2195.5259 56,592 W32tm.exe 03-Apr-2002 02:37 5.0.2195.5011 125,712 Wldap32.dll
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 Windows 2000 Service Pack 4.
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/265173/EN-US/ )The Datacenter Program and Windows 2000 Datacenter Server Product
Article ID: 320711 - Last Review: February 22, 2007 - Revision: 3.7