The "ERROR_INTERNET_CANNOT_CONNECT" error occurs when you send Web requests by using NTLM authentication in Windows 2000

This article was previously published under Q331862
This article applies to Windows 2000. Support for Windows 2000 ends on July 13, 2010. The Windows 2000 End-of-Support Solution Center is a starting point for planning your migration strategy from Windows 2000. For more information see the Microsoft Support Lifecycle Policy.
This article has been archived. It is offered "as is" and will no longer be updated.
When client computers send Web requests by using NTLM authentication to a Microsoft Windows 2000-based computer that is running Microsoft Windows HTTP Services (WinHTTP), the Web requests may not succeed. Additionally, the following error message may be logged in the log file that is generated by the trace configuration tool, WinHttpTraceCfg.exe:
# as an HRESULT: Severity: FAILURE (1), Facility: 0x7, Code 0x2efd
# for hex 0x2efd / decimal 12029 :
This problem occurs because WinHTTP remains in the TIME-WAIT state for some time before releasing a closed connection to be used again. A port must pass the TIME-WAIT state before the port is released. This behavior may cause Windows to run out of dynamic ports because a maximum of 3975 ports are available.

Service pack information

To 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:
260910 How to obtain the latest Windows 2000 service pack

Hotfix information

A 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: Note 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.

File information

The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.
   Date         Time   Version         Size      File name     Platform   --------------------------------------------------------------------   06-Dec-2002  09:19  5.1.2600.1148   310,784   Winhttp.dll   i386   01-Apr-2003  04:42  5.0.2195.6699    89,328   Ndiswan.sys	  i386   14-Mar-2003  06:21          8,944   Spcustom.dll  i386     
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
"NT Lan Manager" protocol

Article ID: 331862 - Last Review: 12/07/2015 13:07:12 - Revision: 1.7

Microsoft Windows 2000 Server, Microsoft Windows 2000 Professional Edition

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbqfe kbwin2ksp4fix kbfix kbbug kbwin2000presp4fix kbprb KB331862