Avatar of LangtechEE
 asked on

OWA problem: Can't view when using anything other than "http://localhost/exchange"

   I have a problem with a Windows 2003 Small Business Server SP2.
Exchange 2003 SP2 is working fine for incomming and outgoing mail.
When I am on the server I can reach OWA by going to

I cannot fully view owa from laptops on the lan or outside the firewall.
when I try going to from another laptop on the network I am given a logon prompt (the non Forms Based Authentication one) and log in. I then see tbe top bar of OWA and nothing else.

Other strange things.
When using firefox I am able to see the mail fine (though of course firefox doesn't support folder browsing)

Also when I am logged onto the server and try to use http://domain.com/exchange I get the same hanging experience as when I am comming from a laptop on the network.

It seems like OWA or IIS is not serving up everything to machines outside of itselft.
I tried reinstalling the virtual directories, but that didn't solve the problem.

this box hasn't been used for awhile and it looks like Forms Based Authentication was somehow turned off, though I'm pretty sure FBA is installed on an SBS box by default.
Also HTTPS doesnt seem to be working either.

thanks for the help
ExchangeSBSMicrosoft IIS Web Server

Avatar of undefined
Last Comment

8/22/2022 - Mon

Have you checked the bindings of the Default Website to see if it is set to respond to requests from (for example) mail.yourcompany.local or mail.yourcompany.com ?

What are your permissions on the Exchange and Exchweb virtual directories? What authentication mechanisms do you have enabled?
Rajith Enchiparambil

If you see your emails while using firefox, OWA works fine internally. Which version of IE are you using? If not IE 7, try updating IE.

For https access, you need to have a certifcate installed to get it working properly. http://www.petri.co.il/configure_ssl_on_owa.htm explains this.

Go through the implementing OWA steps to publish it for outside access

Ok, I made some changes to the exchange and exchweb directories in IIS. Now I after logging in I can see the top and left menu bars, but not the message list. Actually it is sporatic. Twice I got everything to show up. Both times where right after I made a change to the IIS directories.

Here is the current permissions in both IIS directories
Enable Anonymos Access: Not Checked
Basic Authentiation: Checked
Default Domain: \

Enable Anonymos Access: Checked
Basic Authentiation: Not Checked

SSL and Forms Based Authentication is not checked.
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck

Also I am using IE 7 and Firefox 3.
A certificate is not installed.

Just rerun the internet setup wizard from the sbs management console. this should repair any setting that are incorrect in both iss and exchange.

I would like you to run through this ( http://www.msexchange.org/tutorials/Resetting-OWA-Folder-IIS-security-permissions-Exchange-2003.html ) article and make sure that you have all the appropriate permissions and ACL entries applied.

Please let me know what you find.

Also, you may want to start a new question / revoke the points / split them up if you want this thread to get more attention.
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.

Thanks both of you.
I went through both suggestions

Neither seem to have changed much.
I can still access owa locally when logged into the server, though not from another machine on the lan.

I also had to turn off the requirement to use SSL. I'm not sure why, but it seems like something else on the server is trying to use port 443. Not sure what it is.


View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.