When the SOCKS filter is enabled on Microsoft Internet
Security and Acceleration (ISA) Server 2004,
and a client program makes a request for Web server HTTP content, the client
cannot connect to the destination host. You notice
this problem if the client program is configured to use the SOCKS proxy on the
ISA server. When this problem occurs, the connection resets
immediately.
↑ Back to the top
This problem occurs if the connection uses the SOCKS proxy
for a protocol that has an application filter enabled on the ISA server.
For example, if you use SOCKS proxy in ICQ, and ICQ uses HTTP
protocol, port 80, to connect to the ICQ server, the ICQ connection is broken.
This is because ISA Web Proxy is implemented as an application filter that
intercepts HTTP, port 80, connections.
↑ Back to the top
To work around this problem, use ISA Web Proxy instead of
the SOCKS proxy in the client program.
If the client program uses
only the SOCKS proxy, you can use ISA Firewall Client to enable traffic to
reach an external network like the Internet.
↑ Back to the top
Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the "Applies to" section.
↑ Back to the top