Microsoft KB Archive/264504

= Winsock Proxy Clients Do Not Connect Over a Slow Link =

Article ID: 264504

Article Last Modified on 10/31/2006

-

APPLIES TO


 * Microsoft Proxy Server 2.0 Standard Edition

-



This article was previously published under Q264504



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 your Microsoft Winsock Proxy client tries to connect to a Microsoft Proxy server over a slow link (such as a VSAT link), the connection may not be established. When this problem occurs, the Winsock Proxy client receives an &quot;inaccessible server&quot; entry in the Mspclnt.ini file, and the Winsock program does not work.



RESOLUTION
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.

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

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.

The English version of this fix should have the following file attributes or later:

  Date     Time    Version     Size    File name --  05-07-01  17:29  2.0.390.16  96,528  Wspsrv.exe

NOTE: The fix for this problem is to reserve the handle for a fixed amount of time before the proxy server is permitted to reissue the session handle to another client. By default, this time is set to zero seconds and must be changed in the registry for this fix to work properly. Use Registry Editor (Regedt32.exe) to locate the following key in the registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WSPSrv\ Parameters\

Add the following registry value, and then quit Registry Editor:

Value Name: HintHandleTimeout

Data Type: REG_DWORD

Radix: Decimal

Value: Milliseconds

Note that without this registry entry, the default value is zero milliseconds.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
The control channel &quot;connection&quot; is a session ID that is exchanged between the proxy server and the client. It is possible that the same session handle can be given to more than one client. When this occurs, the handles have been given to two clients. The client that can complete the session setup the fastest receives the session handle and the other client receives a negative acknowledgement and must start the negotiation again.

Keywords: kbhotfixserver kbqfe kbbug kbenv kbfix kbqfe KB264504

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.