MercedInfoSys
asked on
OWA SSL Redirect Problem.
I am having troubles getting are OWA SSL Redirect to work. I Am following MS Artical on how to due it. I Can get client to connect just using https:<servername>/exchange. When they use the owhttps.asp they get redirected to the secure page an i get the following error.
"Secure Channel Required This Virtual Directory requires a browser that supports the configured encryption options."
I have verified that my browers can do SSL, I check to make sure it is 128 crypto.
"<%
If Request.ServerVariables("S
Dim strSecureURL
strSecureURL = "https://"
strSecureURL = strSecureURL & Request.ServerVariables("S
strSecureURL = strSecureURL & "/exchange"
Response.Redirect strSecureURL
End If
%>"
"Secure Channel Required This Virtual Directory requires a browser that supports the configured encryption options."
I have verified that my browers can do SSL, I check to make sure it is 128 crypto.
"<%
If Request.ServerVariables("S
Dim strSecureURL
strSecureURL = "https://"
strSecureURL = strSecureURL & Request.ServerVariables("S
strSecureURL = strSecureURL & "/exchange"
Response.Redirect strSecureURL
End If
%>"
ASKER
I forgot to mention that i already edited the 404.3 error for the redirect. The rediect works exept that i get ""Secure Channel Required This Virtual Directory requires a browser that supports the configured encryption options." This just does not make sense to me. It makes it sound like a client side issues. i have tired 10 differnt machines with the newest IE and i still can't connection. But if i just go to the https:// then i can connect.
dont know if this will help but have you restarted your IIS service?
See if you have the require secure channel box checked or unchecked. Under Directory Security tab in the secure communications area click edit. Test it with both and see what happens. In that MS article is says:
If you require SSL on the OWA_Redirect application, the initial HTTP connection cannot be established. Additionally, do not require SSL on the root Web site that contains the OWA_Redirect application.
Not for sure why you would get that error unless you have that box checked. Have to go googling on that one. :)
If you require SSL on the OWA_Redirect application, the initial HTTP connection cannot be established. Additionally, do not require SSL on the root Web site that contains the OWA_Redirect application.
Not for sure why you would get that error unless you have that box checked. Have to go googling on that one. :)
Sorry for another post, had another idea. Just to make sure your browser supports 128 bit: Open IE and click on help then about IE and verify that your Cipher Strength is at 128. Just my 2 cents...hope it helps.
ASKER
I have stopped and start all services related to IIS and yes i have verifed to make sure the browser supports 128bit ciper. I can even go to https://<server>/exchange and it works. That proves that it is not a ciper issues on the client Side. Plus i have tired it on many systems.
ASKER
I also have made sure the require secure communcation is just check on the OWA_redirect Virtual Directory and not the default web site. It actually give you a differnt error if you did that. I tested to make sure.
Sorry, not to be rude or anything but I'm not for sure what "just check" means. The require secure channel box is supposed to be unchecked along with the root web site.
If the box is checked on the the OWA_Redirect the initial HTTP connection cannot be established.
If the box is checked on the the OWA_Redirect the initial HTTP connection cannot be established.
ASKER
Sorry for by bad grammer, It is not check on the default web site and it is checked on the owa_direct virtual directory.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
we also edit the 404.3 error page to redirect
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html>
<head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <meta http-equiv="refresh" content="0;url=https://xxxx.xxx..xxx"> <meta name="GENERATOR" content="Microsoft FrontPage 4.0"> <meta name="ProgId" content="FrontPage.Editor.
</html>