Server Proxy May Fail with Dynamic Packet Filtering (275284)



The information in this article applies to:

  • Microsoft Proxy Server 2.0

This article was previously published under Q275284

SYMPTOMS

When you use Server Proxy for an internal service, Server Proxy may fail if you have multiple external Internet Protocol (IP) addresses and if you enable Dynamic Packet Filtering.

CAUSE

This issue can occur because when a remoted server that uses Server Proxy listens on 0.0.0.0 (INADDR_ANY), WinSock Proxy also listens on 0.0.0.0 on behalf of that server. The computer that is running the WinSock Proxy Service is listening on all addresses; however, a corresponding packet filter is only created for the default external IP address.

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.

STATUS

Microsoft has confirmed that this is a problem in Proxy Server 2.0 and Microsoft Internet Security and Acceleration Server 2000.

MORE INFORMATION

For additional information, click the article number below to view the article in the Microsoft Knowledge Base:

176922 Multiple IP Addresses Cause Dynamic Packet Filter to Fail


Modification Type:MinorLast Reviewed:1/18/2006
Keywords:kbbug kbfix KB275284