Sorry Andy; but it's clear from your questions that you don't understand anything of the sort. Steve, like many of us, is trying to guide you; not spoon-feed you. This alias is composed largely of folks who believe very strongly in the following adage: "Give a man a match and he's warm for a few seconds. Set him on fire and he's warm for the rest of his life." Actually, it's "give a man a fish..." ..you know the rest (or do you need a step-by-step?). We're more than happy to help, but you have to be able to show some self-education along the way. All the publishing scenarios you've run headlong into so far are all described in the ISA help and at the websites I've linked you to. They also include "do this, do that" steps, but what you'll find is that they don't go into "how to build your network", which is clearly what you're in need of. For instance, a quote from your first posting in this tattered thread: "I have Exchange 2003; ISA 2004 Server is doing the FBA for OWA I have tried everything from Microsoft's method of creating a .asp file to inserting a html file which directs the HTTP to HTTPS..." There's nothing in the ISA help or the online docs which directs you to creating custom pages. In fact, doing so is unsupported. -----Original Message----- From: Andrew English [mailto:andrew@xxxxxxxxxxxxxxxxxxxxxx] Sent: Tuesday, February 22, 2005 5:49 AM To: [ISAserver.org Discussion List] Subject: [isalist] RE: HTTP to HTTPS and HTTPS to HTTPS http://www.ISAserver.org I understand the fundamentals on both IIS Websites and ISA publishing Websites. Its just that Steve's explanation is very mish mash to me. When I help people on other forums in times when they need a break down on how-to do something I provide, I don't however provide a mish mash/hack suggestion like Steve does. It's 1. do this, 2. do this, 3. your done! :) Besides if Microsoft wrote things the way Steve did we'd all be in trouble! Andrew -----Original Message----- From: Jim Harrison [mailto:Jim@xxxxxxxxxxxx] Sent: Tuesday, February 22, 2005 1:42 AM To: [ISAserver.org Discussion List] Subject: [isalist] RE: HTTP to HTTPS and HTTPS to HTTPS http://www.ISAserver.org Try reading. There is much to be gleaned from Windows help about how IIS differentiates between web sites. There is also much in the ISA help and MANY documents at http://www.microsoft.com/isaserver/techinfo/guidance/2004.asp http://isaserver.org. ..on how to correctly publish web sites. It isn't "just" ISA any more than its "just" Exchange" or "just" IIS. Granted, no one knows everything, or there wouldn't be a need for this kind of discussion group. Unfortunately, it's quite frustrating to the folks here that try to offer help when your responses are limited to "just give me steps, not references". There are several docs that explain how to publish IIS, Exchange, OWA, RPC/HTTP, ActiveSync and your grandmother's latest porn shots, if you look hard enough (Fruedian?). Take some time, read up and ask specific questions that indicate an effort to go beyond those "I learned everything I know from the sales dewds at CompUSA" skills. -----Original Message----- From: Andrew English [mailto:andrew@xxxxxxxxxxxxxxxxxxxxxx] Sent: Monday, February 21, 2005 8:32 PM To: [ISAserver.org Discussion List] Subject: [isalist] RE: HTTP to HTTPS and HTTPS to HTTPS http://www.ISAserver.org Thanks for the info but its still not very clear.. It seems that it full of assumptions that one knows exactly what you are talking about. Myself and who was it, Dan?, obviously don't. I guess I will have call MS and ask them. Andrew -----Original Message----- From: Steve Moffat [mailto:steve@xxxxxxxxxx] Sent: Monday, February 21, 2005 8:28 PM To: [ISAserver.org Discussion List] Subject: [isalist] RE: HTTP to HTTPS and HTTPS to HTTPS http://www.ISAserver.org OK.....In IIS you have your exchange website, called owa.blah.blah. Your redirect page is set up to redirect to https://owa.blah.blah. In order for this to work, (because you're using FBA ON ISA), the external web address has to open up the redirect page first., therefore you need a completely different site. Call this site what you want, as long as your owa users use this site then the redirect will work. It's all down to your internal dns and host headers. S -----Original Message----- From: Andrew English [mailto:andrew@xxxxxxxxxxxxxxxxxxxxxx] Sent: Monday, February 21, 2005 7:06 PM To: ISA Mailing List Subject: [isalist] RE: HTTP to HTTPS and HTTPS to HTTPS http://www.ISAserver.org Hi Steve, what is the Exchange box is already hosting a website, how does it differentiate between the redirected OWA request website (A)? Can you give me example of this? Thanks Andrew -----Original Message----- From: Steve Moffat [mailto:steve@xxxxxxxxxx] Sent: Monday, February 21, 2005 2:51 PM To: [ISAserver.org Discussion List] Subject: [isalist] RE: HTTP to HTTPS and HTTPS to HTTPS http://www.ISAserver.org Hi Andrew, as you are using FBA on ISA, then the site needs to be redirected back through ISA. Therefore you need to publish a NEW site, with the index page redirecting to the OWA Site. -----Original Message----- From: Ball, Dan [mailto:DBall@xxxxxxxxxxx] Sent: Monday, February 21, 2005 2:00 PM To: ISA Mailing List Subject: [isalist] RE: HTTP to HTTPS and HTTPS to HTTPS http://www.ISAserver.org I don't follow that logic either. I have my Exchange 2003 Server with a hostname of MAIL, my domain name is MAPSNET.ORG, and I published it through my ISA2004 server as MAIL.MAPSNET.ORG, so I know it works. I ran into that same problem, and after pounding my head against the wall for awhile trying to figure it out, it dawned on me what it was. Test it this way: If you can reach your OWA site using the URL http://owa.smoothrunnings.ca/exchange, then you know everything works. Then just add / as a path in your Publishing Rule so it can reach the root IIS directory (on your OWA server) through your publishing rule. -----Original Message----- From: Andrew English [mailto:andrew@xxxxxxxxxxxxxxxxxxxxxx] Sent: Monday, February 21, 2005 12:21 To: [ISAserver.org Discussion List] Subject: [isalist] RE: HTTP to HTTPS and HTTPS to HTTPS http://www.ISAserver.org I don't quite follow you Steve, I make a new website in IIS with any name just as long as it doesn't say owa.smoothrunnings.ca (my OWA sites name) in the host header. And ISA will know to go to this site how? Andrew -----Original Message----- From: Steve Moffat [mailto:steve@xxxxxxxxxx] Sent: Monday, February 21, 2005 11:14 AM To: [ISAserver.org Discussion List] Subject: [isalist] RE: HTTP to HTTPS and HTTPS to HTTPS http://www.ISAserver.org Anything you like as long as it's not the name of the OWA site. -----Original Message----- From: Andrew English [mailto:andrew@xxxxxxxxxxxxxxxxxxxxxx] Sent: Monday, February 21, 2005 11:31 AM To: ISA Mailing List Subject: [isalist] RE: HTTP to HTTPS and HTTPS to HTTPS http://www.ISAserver.org Steve, So I create a new website under IIS, but I give it the host header name of owa.smoothrunnings.ca is that what you are referring too and then redirect it? Andrew -----Original Message----- From: Steve Moffat [mailto:steve@xxxxxxxxxx] Sent: Monday, February 21, 2005 9:21 AM To: [ISAserver.org Discussion List] Subject: [isalist] RE: HTTP to HTTPS and HTTPS to HTTPS http://www.ISAserver.org What you need to do is, create a website (not the owa site), use that site as the front for owa, use that sites index page to redirect to the owa site. To have the site use just the fqdn then, in IIS, in the properties of the owa site, on the home directory tab, select a redirection to an url. In the redirect box, use /exchange, and select the a directory below url entered checkbox. S -----Original Message----- From: Andrew English [mailto:andrew@xxxxxxxxxxxxxxxxxxxxxx] Sent: Monday, February 21, 2005 10:07 AM To: ISA Mailing List Subject: [isalist] HTTP to HTTPS and HTTPS to HTTPS http://www.ISAserver.org Hi, I have Exchange 2003; ISA 2004 Server is doing the FBA for OWA I have tried everything from Microsoft's method of creating a .asp file to inserting a html file which directs the HTTP to HTTPS and everything I try to access http://owa.smoothrunnings.ca I get "page can not be displayed..... forbidden 403". I am thinking its an ISA thing since it is ISA who is doing all the grunt work?? Anyhow I would like to do HTTP to HTTPS and HTTPS without the /exchange to HTTPS with the /exchange. So if someone can help me I would appreciate it. Andrew All mail to and from this domain is GFI-scanned.