Continuing the blogcast series on infrastructure essentials.
With our new rule in place on the ISA Server, this sixth part of configuring TPC over HTTP for Outlook 2003 first takes a quick look at the effects on Outlook Web Access - we now get a basic authentication challenge instead of Forms Basic Authentication. However, we can still log on. We'll come back to that in a few parts time.
Our Outlook profile still has the internal name of our Exchange Server configured for the Exchange Proxy Server, so we alter that to point to the external name, mail.contoso.com. On restarting Outlook with the rpcdiag switch, we see that it connects using RPC over HTTPS through our ISA Server correctly from the Internet. Result!
We put our Outlook profile back to a more "normal" RPC/HTTPS configuration by connecting using TCP/IP on fast networks first, and HTTPS on slow networks first. We then take a look at what happens when we switch our client from internal to external to internal networks. Perfect!
Click here to view.
Series Index:0. Network configuration and series background.1. Getting started2. ISA Server configuration to allow basic web browsing capability3. ISA Firewall Client basic configuration4. ISA Firewall Client auto-detection through WPAD configuration5. Configuring an Exchange mailbox and Outlook profile6. Fixing 0x8004010F on Outlook send/receive7. Installing our first Certificate Authority8. Publishing OWA through ISA using Forms Based Authentication9. OWA /exchange redirection10. OWA nearly goes SSL - we have a certificate11. OWA is available over SSL/HTTPS12. Sending external email - Configuring outbound SMTP13. Mail retrieval through POP3 polling14. Preparations for Email retrieval through SMTP Transfer15. Completing Email retrieval through SMTP Transfer16. RPC/HTTP: Overview and installing RPC Proxy component17. RPC/HTTP: IIS Config and a bit on certificates18. RPC/HTTP: Exchange IIS Config completion19. RPC/HTTP: Working from internal network20. RPC/HTTP: Revisiting our ISA rules