RESOLUTION
To resolve this issue, use the
ProxyBindIp parameter in the Wspcfg.ini file that is configured on the internal server that you are using Server Proxy on. For example, if you are hosting Post Office Protocol 3 (POP3), use a Wspcfg.ini file that is similar to the following example:
[STORE]
ProxyBindIp=110:192.168.1.10
ServerBindTcpPorts=110
Persistent=1
KillOldSession=1
NOTE: The 192.168.1.10 IP address is an example of an address that does work in actual use because it is one of the IP addresses that is part of the assigned Private Ranges.
If you are hosting several services that use the same executable file that is described in the following example, install Proxy Service Pack 1 (SP1), and the fix that is available to resolve this issue (Wspwsp.dll):
[STORE]
ProxyBindIp=110:192.168.1.10,119:192.168.1.10
ServerBindTcpPorts=110,119
Persistent=1
KillOldSession=1
For additional information about the fix that is available to resolve this issue, click the article number below
to view the article in the Microsoft Knowledge Base:
232588 WinSock Proxy Client Fails to Bind Remotely to Proxy Server Computer
You may also need the
ForceCredentials parameter if Access Control is enabled on the WinSock Proxy server.