Skip to main content

Outlook Web Access Loading... in mixed Exchange 2003 and 2007 environment

There are plenty of web sites that can help you resolve now already well known problem in OWA when your browser does not display any pictures in it and hangs with Loading... text.

Use Google to find other resolution if it is not the one described below.

You setup Exchange 2007 into the existing Exchange 2003 environment. You reroute Internet users to use your new Client Access Server (CAS) for OWA. CAS server includes a mechanism that redirects user to the correct Exchange server, being that Exchange 2003 or 2007. It depends on which server the mailbox resides.

In the case that you changed Authentication type on your CAS server such that users don't need to provide domain\username but only username, your Exchange 2003 users could get following screen in their browser...

owa The resolution to the problem is in the authentication type on your CAS server. Not only that you need to change authentication type on your /Exchange folder but also on your /owa and /Exchweb folders.

Authentication

I would also recommend that you enter your domain name on existing /Exchange and /Exchweb Exchange 2003 web folders in IIS if you chose to use only username for login.

Comments

  1. I am also facing the same problem on Exchange 2003. it will be great if you can tell me the solution for the same.
    Thanks
    Saurabh

    ReplyDelete
  2. To solve this problem I fix my IIS configuration. On Exchange virtual directory - Security Tab, enable Basic Authentication and disable Anonymous Access. And ExchWeb Virtual Directory, enable Anonymous Access and disable Basic Authentication.

    Good Luck!!!
    Paulo Sayeg

    ReplyDelete

Post a Comment

Popular posts from this blog

Error "<#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP#" when you send attachment in your mail

Some users were receiving error <#5.5.2 smtp;554 5.5.2 Invalid data in message> #SMTP# when they sent message with attachment. The problem is when attached document name is longer than 50 characters. Some Firewalls have header size restriction and that limit blocks this messages to be sent. To correct this, change header limit on affected Firewall or shorten the name of the document you are sending (which is probably not good permanent solution).******
Update #1: Default header size limit in Exchange 2007 is 64K.Update #2: It might be the SMTP version problem. Mail is rejected with CONTENT-DISPOSITION error (overly long message header field for CONTENT-DISPOSITION) but not for all SMTP servers (same mail sent through different SMTP servers). If you send mail with attachment that has name longer than 50 characters from Exchange 2007 directly through DNS you may encounter this error, but if you send same mail from Exchange 2007 through smart host (other than Exchange) mail is d…

Change SMTP port 25 in Exchange 2007, 2010

For some reason you might want to change default SMTP port number 25 Exchange 2007 is using. Exchange 2007 uses RECEIVE AND SEND connectors, one for receiving mails and other for sending mails (obviously ;)
So you need to change ports on those connectors. I will not say those two, because you might be using more than two.
You change Receive connector port by opening the connector properties in Exchange Management Console --> Hub Transport --> RECEIVECONNECTORNAME --> Properties --> Network --> Local IP Addresses (Edit Receive Connector Binding)
Just to clarify what "Local IP Addresses" and "Remote Servers" are (from Exchange 2007 help), because I find it little bit confusing: Use these local IP Addresses to receive mail Use this list to specify the IP addresses and port numbers on which this Receive connector listens for incoming mail. Receive mail from remote servers which have these IP addresses Use this list to specify the remote IP address range fr…

The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup

You get this error "The Windows component Server-Gui-Mgmt-Infra isn't installed on this computer and needs to be installed before Exchange setup" when you try to install Exchange 2016 on Windows 2016 server. Exchange 2016 pre CU3 does not support Windows 2016, therefore you need to download Exchange 2016 CU3, which is in fact full copy of Exchange 2016 server in order to install it on Windows 2016 machine.