Discussion Locked

OWA from the outside world via SSL..

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

As some of you know I have been planning to make OWA (Outlook Web Access) accessible from the out side world via Secure Sockets Layer or HTTPS. Here is were I am at so far..
Windows 2000 server with a SSL certificate, OWA is installed, right now Exchange server is installed too. I am able to use "https://owa-server" to see a test file that I made, default.htm, as well as logon.asp, yet after I logon through the logon.asp page I am unable to see my e-mail box, a blank screen appears. What am Idoing wrong? Do I need to have Exchange server loaded or can I take it off? Please help.

8 replies

by paskettj

Your clue may lie in how SSL works. Do you by chance have 128 Bit Cipher strength on your browser?

by bizaro_aaron_wurthmann

Considering the fact that I can get to my test page as well as the logon.asp page I'm going to have to say yes my browser is working fine.

Thanks, any other ideas?

by aaron_wurthmann

Okay here is the deal.. I got tired of looking at the machine and I decided to start all over again, upon starting all over again I realized the error of my ways. On my first install I install OWA without Exchange and when I tested it didn't work soI thought I should try with Exchange on. (remember this is a windows 200 box) It still didn't work, then I realized that didn't put the services packs on. (windows 2000 requires sp3). Afterward I uninstalled Exchange. Of course it was too late, OWA had binded to the local Exchange server, hence the blank page when I tested it. When began the second time around I didn't install Exchange and after the OWA install I put SP3 on all is well. Thank you everyone.

by mckaytech

It's not necessary to have Exchange installed on the OWA/IIS server unless you want to use NTLM authentication. As long as there is not an intervening firewall, it should just be a point and shoot sort of thing since you're apparently using Basic over SSL authentication.

I've spent some time recently immersed in Microsoft's White Paper on OWA implementation and based on that and my recent experience, the only thing I can suggest to check is that the user account you are using has the Log onLocally right on the IIS server.

paul

by guy

Two ideas
1) Are you using outlook? If so have you enabled / disabled the SSL: Go to Outlook, Tools, Account, Properties, Advanced.

2) Wild idea have you changed any DNS settings?

This discussion is closed to new replies.