Summary


Server publishing rules allow you to publish almost any protocol. This is the primary advantage of server publishing over Web publishing. The server publishing rule essentially performs a reverse NAT function. The ISA server does not replace the source IP address on the packet unless you implement the changes noted in Microsoft KB article Q311777. An important consideration when implementing server publishing rules is that you need to avoid port contention on the external interface. No two services can listen on the same port on the same IP address on the external interface of the ISA server. For this reason, you typically need to disable the IIS services on the ISA server. You can also use server publishing rules to publish Web sites. The most common reason for doing this is so that the original client IP address appears in the Web server's log files.

Web publishing rules allow you to publish Web and FTP sites. Web publishing rules are handled by the Web Proxy service. The Web Proxy service is able to examine the application-layer data and make decisions on how to handle requests based on information such as the destination URL. Web publishing rules also allow you to perform port and protocol redirection. Protocol redirection allows you to bridge HTTP requests as SSL or FTP requests. Port redirection allows you to accept requests on the port number on the external interface and then forward them to another port on an internal network Web server. The main drawback of Web publishing rules is that the client's source IP address is always changed to the internal IP address on the ISA server.




The Best Damn Firewall Book Period
The Best Damn Firewall Book Period
ISBN: 1931836906
EAN: 2147483647
Year: 2003
Pages: 240

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net