Microsoft KB Archive/232588
Article ID: 232588
Article Last Modified on 10/17/2005
- Microsoft Proxy Server 2.0 Standard Edition
This article was previously published under Q232588
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.
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.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
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.
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 that is 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:55AM 138 KB Wspwsp.dll Intel 6/16/99 07:54AM 257 KB Wspwsp.dll Alpha
Microsoft has confirmed that this is a problem in Proxy Server 2.0.
For additional information about Proxy Server 2.0, click the article number below to view the article in the Microsoft Knowledge Base:
259491 Winsock Proxy Client May Not Start
Additional query words: Q181420
Keywords: kbbug kbfix kbqfe kbhotfixserver KB232588