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
SYMPTOMSOn 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.CAUSEThis problem occurs because the WLDAP32!LdapBind method hard codes 120 seconds as the BindTimeout value.RESOLUTIONHotfix informationA 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. PrerequisitesNo prerequisites are required. Restart requirementYou must restart the computer after you apply this hotfix. Hotfix replacement informationThis 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. |
Adsldp.dll | 5.0.2195.6613 | 125,712 | 19-Jun-2003 | 05:05 | x86 | Adsldpc.dll | 5.0.2195.6701 | 133,904 | 19-Jun-2003 | 05:05 | x86 | Adsmsext.dll | 5.0.2195.6667 | 62,736 | 19-Jun-2003 | 05:05 | x86 | Advapi32.dll | 5.0.2195.6876 | 388,368 | 23-Mar-2004 | 11:17 | x86 | Browser.dll | 5.0.2195.6866 | 69,904 | 23-Mar-2004 | 11:17 | x86 | Dnsapi.dll | 5.0.2195.6824 | 134,928 | 23-Mar-2004 | 11:17 | x86 | Dnsrslvr.dll | 5.0.2195.6876 | 92,432 | 23-Mar-2004 | 11:17 | x86 | Eventlog.dll | 5.0.2195.6883 | 47,888 | 23-Mar-2004 | 11:17 | x86 | Kdcsvc.dll | 5.0.2195.6890 | 143,632 | 23-Mar-2004 | 11:17 | x86 | Kerberos.dll | 5.0.2195.6903 | 210,192 | 10-Mar-2004 | 11:37 | x86 | Ksecdd.sys | 5.0.2195.6824 | 71,888 | 20-Sep-2003 | 09:32 | x86 | Lsasrv.dll | 5.0.2195.6987 | 513,296 | 15-Oct-2004 | 03:16 | x86 | Lsass.exe | 5.0.2195.6902 | 33,552 | 25-Feb-2004 | 08:59 | x86 | Msv1_0.dll | 5.0.2195.6897 | 123,152 | 10-Mar-2004 | 11:37 | x86 | Netapi32.dll | 5.0.2195.6949 | 309,008 | 10-Jun-2004 | 01:58 | x86 | Netlogon.dll | 5.0.2195.6891 | 371,472 | 23-Mar-2004 | 11:17 | x86 | Ntdsa.dll | 5.0.2195.6896 | 1,028,880 | 23-Mar-2004 | 11:17 | x86 | Samsrv.dll | 5.0.2195.6897 | 388,368 | 23-Mar-2004 | 11:17 | x86 | Scecli.dll | 5.0.2195.6893 | 111,376 | 23-Mar-2004 | 11:17 | x86 | Scesrv.dll | 5.0.2195.6903 | 253,200 | 23-Mar-2004 | 11:17 | x86 | Sp3res.dll | 5.0.2195.7040 | 6,309,376 | 20-Apr-2005 | 19:07 | x86 | W32time.dll | 5.0.2195.6824 | 50,960 | 23-Mar-2004 | 11:17 | x86 | W32tm.exe | 5.0.2195.6824 | 57,104 | 20-Sep-2003 | 09:32 | x86 | Wldap32.dll | 5.0.2195.7059 | 127,248 | 10-Jul-2005 | 14:18 | x86 |
STATUSMicrosoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 7/26/2006 |
---|
Keywords: | kbHotfixServer kbBug kbfix kbQFE kbWin2000preSP5fix kbpubtypekc KB897711 kbAudITPRO |
---|
|