Enabling Web Publishing Fails to Forward Web Server Requests (282031)


The information in this article applies to:

  • Microsoft Proxy Server 2.0
This article was previously published under Q282031

SYMPTOMS

After enabling Web Publishing in Proxy Server 2.0, and selecting "sent to another Web server" to specify the name, or IP Address of an internal Web server, incoming Web server requests are not forwarded to the internal Web server. Web clients obtain the default page on the Proxy server instead of the one on the internal Web server when the Web browser accesses the external IP address on the Proxy server.

CAUSE

This behavior occurs due to one of the following reasons:
  1. The Internet Server API (ISAPI) filter is not initialized. To verify this, in the properties of the default Web site, on the ISAPI Filters tab, the status of the w3proxy filter does not show a green arrow pointing up.

    -OR-
  2. The Proxy server's external IP address is included in the LAT table.

RESOLUTION

To resolve this behavior, use the appropriate resolution:
  1. If the w3proxy filter is not initializing, make sure that the W3proxy.dll exists in the InetPub\scripts\proxy folder, and that it is not corrupt (check the file version). If you are using more than one filter, move the w3proxy filter to the top.

    -OR-
  2. Remove the Proxy server's external IP address from the LAT table.
Modification Type:MinorLast Reviewed:1/18/2006
Keywords:kbnetwork kbpending kbprb KB282031
©2004 Microsoft Corporation. All rights reserved.