asked on 10th Aug 2011 | 1 Answers | Answer It!
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.
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: Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. Click Start, click Run, type regedit in the Open box, and then click OK.
1. Navigate to the following registry subkey:
2. In the right pane of Registry Editor, right-click RequestTimeoutSecs, and then click Modify.
3. 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.
4. Click OK, and then restart the World Wide Web Publishing service. To restart this service:
a. Click Start, click Run, type cmd in the Open box, and then click OK.
b. Type net stop iisadmin /y, and then press ENTER.
c. 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.
5. 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.
6. If you still experience the timeout problems, start Registry Editor (if it is not already started), and then navigate to the following registry subkey:
7. In the right pane of Registry Editor, right-click SocketIoTimeoutSecs, and then click Modify.
8. 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.
9. Restart the World Wide Web Publishing service.
10. 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.
11. Add the TcpMaxDataRetransmissions value to the Windows registry.
Here’s to Good Karma
asked on 16th Aug 2011 | 1 Answer
asked on 15th Aug 2011 | 1 Answer
Here's to Good Karma