ISA & OWA HTTPS issue.

[lck092580]

Hey,

I've successfully set up OWA behind ISA server last week and have also installed a secure certificate to secure the access. I have set ISA server to reject access via http so all users must access using https.

The problem I'm having is that many users are "confused" or "assume" that the server is unavailable when they forget to access it via https. I am aware of a solution (which is posted on MS's knowledge base) that creates an asp page to forward all http requests to https. However, this solution was not written for ISA server because it relies on IIS to handle the redirection (in my case, ISA rejects the request and not allow it to reach IIS).

Does anyone know how I can use asp page which redirects all requests to https on ISA? Thanks.

T

 

[LJMoore]

This will sound like an odd "response" to your question because it is actually a question. I am trying to do what you have successfully done. While searching for a solution I saw your problem. I read with interest your comment about:

"I am aware of a solution (which is posted on MS's knowledge base) that creates an asp page to forward all http requests to https. However, this solution was not written for ISA server because it relies on IIS to handle the redirection (in my case, ISA rejects the request and not allow it to reach IIS)."

I am running a multi-homed ISA server (internal and external address) and am presently running OWA on my Exchange server (internal address only). DNS is done internally from our DNS W2K domain controller. The problem I am experiencing is that I can access OWA internally using HTTPS only (because of the asp page I set up - which is what we want to happen) but I cannot access it externally using either http or https. Am I blocking people from the outside from accessing the OWA server because I set up that asp???? Could it be that simple?? It sounds like my scenario is similar to yours.

Thank you,
L Moore

 

[lck092580]

Hi Moore,

Your problem seems to be an issue regarding the request forwarding that's supposed to be done with ISA. How are you able to access the exchange server internally? Are you doing it by entering the internal ip?

If u're able to access it via its internal ip then, this may sound obvious, you probably haven't created the approriate web/server (yes u can do it both ways) publishing rules. Remember that you must open ports and direct the appropriate requests to ur exchange server, else, all requests to, say,

http://www.moore.com/exchange

would be dropped @ the ISA server.

Here is a link that gives u directions as to how you should publish ur exchange server:

http://support.microsoft.com/default.aspx?scid=kb;en-us;290113

Feel free to tell me if this is the solution u're looking for.

T