I know people have done this quite a bit. Don't know about that specific hardware though. Does OWA work on the FE without the SSLA?
======================================================= Andy Webb [EMAIL PROTECTED] www.swinc.com Simpler-Webb, Inc. Austin, TX 512-322-0071 ======================================================= -----Original Message----- From: Info1 Team [mailto:[EMAIL PROTECTED]] Sent: Friday, September 20, 2002 4:39 PM To: Exchange Discussions Subject: Exchange 2000 ssl accelerator Anyone ever been successful deploying E2k in a front end/back end scenario with the front end box in a DMZ along with a hardware ssl accelerator? Can't get OWA to work correctly. You get prompted for authentication twice and then you can get into OWA, but Exchange automatically redirects it to a http vice an https connection. It's the exact same problem that is outlined in the below Q article. The only problem is that we aren't running a proxy server and there is no way on the h/w accelerator box to add the header. OWA will be the primary means of accessing corporate email and we need the functionality provided by the hardware SSL accelerator to handle all the SSL encryption/decryption with as many connections as possible vice limiting the number of connections using traditional IIS SSL. E2k Enterprise svc pk 3 Win2k Svc Pk 3 Intel Netstructure 7110 hardware accelerators PSS ID Number: Q260772 Article last modified on 09-18-2000 winnt: winnt ====================================================================== ------------------------------------------------------------------------ ------- The information in this article applies to: - Microsoft Exchange 2000 Server ------------------------------------------------------------------------ ------- SYMPTOMS ======== When you use Microsoft Outlook Web Access (OWA) with Secure Sockets Layer (SSL) enabled to connect to a front-end Exchange 2000 Server computer that is running behind a proxy server, the SSL connection may not be successful. This problem may also occur when you are using only a back-end Exchange 2000 Server computer. CAUSE ===== This problem can occur because SSL or HTTPS requests arrive at the back-end Exchange 2000 Server computer on port 80 instead of arriving at the front-end Exchange 2000 Server computer. Redirects are returned as "http://"; instead of "https://";. RESOLUTION ========== To resolve this problem, configure the proxy server to add the following header on upstream requests when OWA SSL requests are on port 443: FrontendHTTPS:ON STATUS ====== Microsoft has confirmed this to be a problem in Microsoft Exchange 2000 Server. Additional query words: xmrp ====================================================================== Keywords : Component : WebClient Version : winnt: Platform : winnt Issue type : kbbug Solution Type : kbnofix ======================================================================== ===== Copyright Microsoft Corporation 2000. _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
