In this article we’ll carry out some procedures to allow the front-end Exchange Server to accept incoming connections from Internet based hosts and allow the front-end Exchange Server access to the domain controller and back-end Exchange Server on the corporate network.
In this, part 4 of the series, we’ll continue configure the ISA firewall with Web Publishing Rules to allow incoming connections to the front-end Exchange Server’s Web sites.
ISA 2004 provides a very secure method for publishing Outlook Web Access (OWA) web sites for your Exchange Server. There are lots of articles on this site that provide tutorials on how to do this, and it works very well, with only one minor problem having to do with the spelling checker. This article documents what the problem is and a workaround for solving it.
In this, part 3 of the series, we will go over the often misunderstood areas of certificate naming conventions and DNS infrastructure required to support the configuration. This is an area of common confusion, so pay very close attention to the concepts discussed in this article. Once you understand the concepts and issues related to a proper certificate naming infrastructure, you’ll never again have to wonder why your secure Web and Server Publishing Rules don’t work correctly.
In this article we’ll go step by step through a typical ISA 2004 troubleshooting scenario. We’ll show how to use ISA 2004’s new logging feature as your #1 troubleshooting tool.
In part 1 of this article series on configuring a multihomed ISA firewall to support multiple DMZ segments, we went over DMZ design principles and discussed the different types of DMZs the ISA firewall can support. We also went over in detail the differences between authenticated access and anonymous DMZ segments, and how we can securely place a front-end Exchange Server on an authenticated access DMZ while removing the front-end Exchange Server from the same security zone on which the back-end Exchange Server lies.