The information in this article applies to:
SYMPTOMSA Winsock application may to fail to bind to a remote port on a Proxy Server computer when the Winsock application is running on the Winsock client and a remote bind is specified in the Wspcfg.ini file. CAUSE
The entry of ServerBindTCPPorts in the Wspcfg.ini file allows a Winsock application to bind to the local ports and to the specified port on the Proxy Server computer. A call to Bind() with INADDR_ANY means that the Winsock application will accept incoming requests on any local interface and send requests on the "most appropriate" local interface. RESOLUTIONA supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web: http://support.microsoft.com/support/supportnet/default.asp NOTE: This hotfix should be applied to the Proxy server. Also, after the fix has been applied, the Winsock Proxy client must be reinstalled on the computer trying to bind to the proxy server in such a manner that the new version of the Wspwsp.dll file is copied to the client computer. The English version of this fix should have the following file attributes or later:
STATUSMicrosoft has confirmed this to be a problem in Proxy Server 2.0. Additional query words: Q181420
Keywords : |
Last Reviewed: November 16, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |