"10060 Connection Timed Out" Error Message When You Try to Connect to Certain Web Sites (811087)


The information in this article applies to:

  • Microsoft Proxy Server 2.0, when used with:
    • the operating system: Microsoft Windows NT 4.0
  • Microsoft Windows NT Server 4.0
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

When a Web Proxy client tries to connect to certain Web sites, one of the following error messages may appear in the browser window:
The page cannot be displayed

There is a problem with the page you are trying to reach and it cannot be displayed.

Please try the following:
  • Click the Refresh button or try again later.
  • Open the file:// home page, and then look for links to the information you want.
  • If you believe you should be able to view this directory or page, please contact the Web site Administrator by using the e-mail address or phone number listed on the file:// home page.

10060 - Connection timeout
-or-
HTTP Error 404404 Not Found

The Web server cannot find the file or script you asked for. Please check the URL to ensure that the path is correct.

Please contact the server's administrator if this problem persists.
If you click the Refresh button, the Web page may open successfully. Additionally, if you install the Winsock Proxy client on the client computer, the problem does not recur.

CAUSE

This behavior may occur when the Web Proxy service connection settings do not allow enough time to receive a response from the destination Web site before the service closes the connection.

By default, the Web Proxy service waits for 60 seconds on initial connection attempts to a Web site and all later "GET" requests for a response from the server, and it waits 120 seconds before it times out idle socket connections.

RESOLUTION

To resolve this issue, follow these steps:

Step 1: Troubleshoot the Web Proxy Connection

Determine if this issue occurs only when the Web Proxy service is used. To do this, install the Winsock Proxy Client on the client computer, disable the Web Proxy settings (under Local Area Network [LAN] settings on the Connections tab of the Internet Options dialog box), and then try to go to the Web site where you experience the problem. If you can reach the site successfully, the problem is with the Web Proxy timeout settings. If so, go to the next step.

Step 2: Increase the Web Proxy Timeout Settings

To increase the amount of time that the Web Proxy service waits before it closes idle sessions, follow these steps: WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
  1. Click Start, click Run, type regedit in the Open box, and then click OK.
  2. Navigate to the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3Proxy\Parameters

  3. In the right pane of Registry Editor, right-click RequestTimeoutSecs, and then click Modify.
  4. Click Decimal, and then type the number of seconds that you want the Web Proxy service to wait for a response before it returns an error message. A recommended value for this setting is 180 or more.
  5. Click OK, and then restart the World Wide Web Publishing service. To restart this service:
    1. Click Start, click Run, type cmd in the Open box, and then click OK.
    2. Type net stop iisadmin /y, and then press ENTER.
    3. When the service has stopped successfully, type net start iisadmin /y, and then press ENTER.

      Note You may have to restart additional dependent services that were stopped together with the IIS Admin Service.
  6. Test the new settings from a client computer that is configured to use the Web Proxy service: try to go to the Web site where you experienced the problem. If the issue is not resolved, go to the next step.
  7. If you still experience the timeout problems, start Registry Editor (if it is not already started), and then navigate to the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3Proxy\Parameters

  8. In the right pane of Registry Editor, right-click SocketIoTimeoutSecs, and then click Modify.
  9. Click Decimal, and then type a value of 300 (or more) in the Value data box.

    Note This is the time in seconds that the Web Proxy service will wait before ending idle socket connections.
  10. Restart the World Wide Web Publishing service.
  11. Test the new settings from a client computer that is configured to use the Web Proxy service: try to go to the Web site where you experienced the problem. If the issue is not resolved, go to the next step.
  12. Add the TcpMaxDataRetransmissions value to the Windows registry. For additional information about how to add and configure this value, click the following article number to view the article in the Microsoft Knowledge Base:

    191143 10060 Connection Timed Out Error with Proxy Server on Slow Link

Modification Type:MinorLast Reviewed:8/4/2003
Keywords:kberrmsg kbprb KB811087
©2003 Microsoft Corporation. All rights reserved.