In a nutshell, I wouldn't do it because an Exchange 5.5 OWA server talks MAPI to the Exchange server, so needs a whole crapload of ports to be opened. You should implement a VPN. You can get a pretty good one for free with Windows 2000 Server.
Ed Crowley MCSE+Internet MVP Tech Consultant Compaq Computer Corporation (soon to be HP) All your base are belong to us. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Timothy J. Trace Sent: Thursday, November 01, 2001 6:49 PM To: Exchange Discussions Subject: OWA Newbie Greetings: I've would greatly appreciate some help planning an OWA implementation. I've heard that there's a few experts here who might be able to help... Here's some specifics of my situation: I've got a back-to-back DMZ using ISA 2000 Server Standard Edition. The ISA Server Systems, and the DMZ systems, are not attached to any domain, and rely on public DNS or straight IP addressing. There's an IIS 5.0 server in the DMZ that hosts a number of websites, and a few apps which pull information from a SQL server located on my private network. That's all working correctly. The DMZ IIS server also serves as my inbound SMTP relay, and it's working correctly as well. For many reasons, cost included, that IIS server is a very attractive choice for OWA. So here's the big question: what's my best approach for implementing OWA? Ease of implementation, security and reliability are concerns, in that order. Thanks very much, in advance, Tim == _________________________________________________________________ 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]
