You cannot configure the time-out value by using the LDAP_OPT_TIMELIMIT session option on a Windows 2000 SP4-based computer (897711)



The information in this article applies to:

  • Microsoft Windows 2000 Server SP4
  • Microsoft Windows 2000 Professional SP4
  • Microsoft Windows 2000 Advanced Server SP4

SYMPTOMS

On a Microsoft Windows 2000 Service Pack 4 (SP4)-based computer, you cannot configure the time-out value by using the LDAP_OPT_TIMELIMIT session option.

CAUSE

This problem occurs because the WLDAP32!LdapBind method hard codes 120 seconds as the BindTimeout value.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone 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.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
File nameFile versionFile sizeDateTimePlatform
Adsldp.dll5.0.2195.6613125,71219-Jun-200305:05x86
Adsldpc.dll5.0.2195.6701133,90419-Jun-200305:05x86
Adsmsext.dll5.0.2195.666762,73619-Jun-200305:05x86
Advapi32.dll5.0.2195.6876388,36823-Mar-200411:17x86
Browser.dll5.0.2195.686669,90423-Mar-200411:17x86
Dnsapi.dll5.0.2195.6824134,92823-Mar-200411:17x86
Dnsrslvr.dll5.0.2195.687692,43223-Mar-200411:17x86
Eventlog.dll5.0.2195.688347,88823-Mar-200411:17x86
Kdcsvc.dll5.0.2195.6890143,63223-Mar-200411:17x86
Kerberos.dll5.0.2195.6903210,19210-Mar-200411:37x86
Ksecdd.sys5.0.2195.682471,88820-Sep-200309:32x86
Lsasrv.dll5.0.2195.6987513,29615-Oct-200403:16x86
Lsass.exe5.0.2195.690233,55225-Feb-200408:59x86
Msv1_0.dll5.0.2195.6897123,15210-Mar-200411:37x86
Netapi32.dll5.0.2195.6949309,00810-Jun-200401:58x86
Netlogon.dll5.0.2195.6891371,47223-Mar-200411:17x86
Ntdsa.dll5.0.2195.68961,028,88023-Mar-200411:17x86
Samsrv.dll5.0.2195.6897388,36823-Mar-200411:17x86
Scecli.dll5.0.2195.6893111,37623-Mar-200411:17x86
Scesrv.dll5.0.2195.6903253,20023-Mar-200411:17x86
Sp3res.dll5.0.2195.70406,309,37620-Apr-200519:07x86
W32time.dll5.0.2195.682450,96023-Mar-200411:17x86
W32tm.exe5.0.2195.682457,10420-Sep-200309:32x86
Wldap32.dll5.0.2195.7059127,24810-Jul-200514:18x86

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

816915 New file naming schema for Microsoft Windows software update packages

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates


Modification Type:MinorLast Reviewed:7/26/2006
Keywords:kbHotfixServer kbBug kbfix kbQFE kbWin2000preSP5fix kbpubtypekc KB897711 kbAudITPRO