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.

Labels:

Comments

  1. AnonymousSeptember 18, 2008 at 9:42 AM

    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. AnonymousSeptember 23, 2008 at 3:17 AM

    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

Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}]

 If you got this error checking the mail flow for a distribution group, it means the distribution group is closed and only internal senders can send e-mail to this group. When outside user sends e-mail to this group you get  Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}] Set Delivery for this group to internal and external users and your problem will be solved. 
Read more

Netscaler vs Exchange 2019 "time out during ssl handshake stage

If you are using Citrix Netscaler as load balancer in front of Exchange 2019 server you must know this: Microsoft Exchange 2019 is secured by default and allows only TLS 1.2. Therefore default schannel settings are as follows (using IISCrypto tool from Nartac Software): While Citrix Netscaler offers following Cipher Suites: TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 TLS_DHE_DSS_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5 TLS_DH_anon_WITH_DES_CBC_SHA TLS_DH_anon_WITH_AES_128_CBC_SHA TLS_DH_anon_WITH_AES_256_CBC_SHA TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA Now, you will fi...
1 comment
Read more

Ports that need to be open on Firewall for Edge Transport servers

Ports that need to be open on firewall for Edge Server subscription with Hub Server to function properly: For Inbound traffic: SMTP - TCP port 25 (from Internet) SMTP - TCP port 25 (from Edge server to Hub server on internal network) For Outbound traffic: SMTP - TCP/UDP port 25 (from Edge to Internet) SMTP - TCP/UDP port 25 (from Hub to Edge server) LDAP for EdgeSync - TCP port 50389 (from Hub to Edge server) Secure LDAP for EdgeSync - TCP port 50636 (from Hub to Edge server) Since Edge server needs to communicate with Hub server it is important that it can resolve Hub transport servers by FQDN and Hub transport servers must be able to resolve Edge servers by its FQDNs. To accomplish this you need to either open 53 (DNS) port and configure internal network adapter to use internal DNS but as a security precaution I would suggest to enter DNS records for Edge servers on local DNS manually and to fill hosts file on Edge servers with FQDNs for Hub transport servers.
2 comments
Read more