Winsock Proxy Client Fails to Bind Remotely to Proxy Server Computer

ID: Q232588

The information in this article applies to:

SYMPTOMS

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

When a Winsock application is running on the Microsoft Winsock Proxy client and the Winsock application calls the Winsock function Bind() with 0.0.0.0 or INADDR_ANY, the call fails and returns an error to the Winsock application. If the application specifies the local address in the Bind() call, the call succeeds.


RESOLUTION

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

   Date      Time                 Size    File name     Platform
   -------------------------------------------------------------
   6\16\99   07:54AM               95KB   Wspsrv.exe    x86
   6\16\99   07:55AM              138KB   Wspwsp.dll    x86
   6\16\99   07:53AM              170KB   Wspsrv.exe    alpha
   6\16\99   07:54AM              257KB   Wspwsp.dll    alpha

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, and if it is determined that you only require the fix you requested, no fee will be charged. However, if you request additional technical support, and if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support, you may be charged a non-refundable fee.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:
Q154871 Determining If You Are Eligible for No-Charge Technical Support


STATUS

Microsoft has confirmed this to be a problem in Proxy Server 2.0.

Additional query words: Q181420 


Keywords          : 
Version           : winnt:2.0
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: August 11, 1999