I'm not exactly sure. The MS article doesn't have you do anything with paths. It also doesn't have you create two OWA rules (Basic and NTLM). I think those were the primary differences. (I didn't go through Tom's articles regarding getting and installing the cert, cause I had that done already and was pretty confident it was right.) Rob From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On Behalf Of Jerry Young Sent: Tuesday, November 25, 2008 2:44 PM To: isalist@xxxxxxxxxxxxx Subject: [isalist] Re: Problem accessing Exch 2007 OWA Let me guess, the issue was a path setting not being in place? On Tue, Nov 25, 2008 at 2:19 PM, Rob Moore <RMoore@xxxxxxxx> wrote: Never mind. I did what I should have done in the first place - follow Tom's articles. (The length and number of them had intimidated me previously. Of course, with all the screenshots, they just aren't that bad. Plus it's way easier than following the MS articles.) Now it works! Thanks, Rob _____________________________________________ From: Rob Moore Sent: Tuesday, November 25, 2008 12:50 PM To: 'isalist@xxxxxxxxxxxxx' Subject: Problem accessing Exch 2007 OWA Hello List- Using ISA 2006 Standard, SP1, on Windows Server 2003 SP2 (domain member). I'm trying to publish our new Exchange 2007 server. I've been following the directions from Microsoft, Publishing Exchange Server 2007 with ISA Server 2006 (technet.microsoft.com/en-us/library/bb794751.aspx). I've gone through the whole procedure and have run into a problem. When I try to go to https://webmail.afsc.org/owa from outside the network, I get an error that says Internet Explorer cannot display the webpage, as if it were a DNS error (the error page is a generic IE error page, not an ISA error page). However, if I ping webmail.afsc.org <http://webmail.afsc.org/> , the computer tries to ping the correct address, so I don't believe it's a DNS issue. When I monitor what's happening, I come up with this error: 0x800733f5 WSA_RWS_ERROR_ACCESS_DENIED (the whole entry is below), which is coming from my default rule. Googling that error doesn't give me many results, and most of those are in Russian (or something). Any help with what might be going on? For what it's worth, I've got a rule publishing SSL OWA on Exchange 2003 that works just fine. Here's the whole entry from monitoring the activity on ISA: Original Client IP Client Agent Authenticated Client Service Server Name Referring Server Destination Host Name Transport MIME Type Object Source Source Proxy Destination Proxy Bidirectional Client Host Name Filter Information Network Interface Raw IP Header Raw Payload GMT Log Time Source Port Processing Time Bytes Sent Bytes Received HTTP Status Code Cache Information Log Record Type Authentication Server Log Time Destination IP Destination Port Protocol Action Rule Client IP Client Username Source Network Destination Network HTTP Method URL Result Code Error Information 209.120.230.106 <http://209.120.230.106/> PHL-ISA3 - TCP - - 11/25/2008 4:49:40 PM 2383 0 0 0 0x0 Firewall - 11/25/2008 11:49:40 AM 209.120.230.118 <http://209.120.230.118/> 443 HTTPS Denied Connection Default rule 209.120.230.106 <http://209.120.230.106/> External Local Host - - 0x800733f5 WSA_RWS_ERROR_ACCESS_DENIED 0x0 Thanks, Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rob Moore Network Manager 215-241-7870 Help Desk: 800-500-AFSC -- Cordially yours, Jerry G. Young II Microsoft Certified Systems Engineer