General discussion

Locked

OWA delay on frontend backend config

By apichot ·
When I access OWA 2003 on our front-end server it is very slow to load messages once clicked or to do just about anything for that matter. It I access OWA directly off the backend server where my box is located than everthing is very fast no delay. Both the front and backend servers are exchange2003. The backend is a windows 2003 cluster. Why is it taking the front end soo long to proxy the request from the backend and serve it up to the client?

This conversation is currently closed to new comments.

4 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by BFilmFan In reply to OWA delay on frontend bac ...

Several questions here, what is the load on the front-end server for memory and processor and network?

Did you mean that when you access the back-end server via a MAPI connection it is fast? This is to be expected.

Or did you set up OWA on the back-end server and test it? If it responds well here, it means you have an issue with the front-end or network connectivity.

The steps in this guide may be of assistance in determining the exact cause of your issues:

http://www.microsoft.com/technet/prodtechnol/Exchange/guides/E2k3FrontBack/ac86ec54-a60a-4743-b723-da9e557e07b9.mspx

And Troubleshooting OWA:
http://www.microsoft.com/technet/prodtechnol/exchange/2000/support/troubowa.mspx

Collapse -

by apichot In reply to

I had looked at those documents in advance and did not find any useful info.

Collapse -

by apichot In reply to OWA delay on frontend bac ...

I connected to the backend server using OWA. I had reviewed both documents that you suggested before posting. The do not address proformance issues mostly just errors. The load on the front end servers is not high. The delay seems to be in the front-end server getting the info from the backend server.

Collapse -

by BFilmFan In reply to OWA delay on frontend bac ...

On your back-end servers, do you allow HTTP requests, or did you close this off as Microsoft suggests?

When you look at performance monitor on the front-end server, what are you seeing?

Is there a firewall between the FEP and BEP?

How many client connections are being made between the FEP and BEP's and did you size the hardware via the Microsoft spreadsheet?

Also, you may want to try these steps:

1. Click "Start", point to "Programs", point to "Microsoft Exchange", and then click "System Manager".
2. Expand "Servers", expand "<ServerName>", expand "Protocols", and then expand "HTTP".
3. Right-click "Exchange Virtual Server", and then click "Properties".
4. Click the "Settings" tab.
5. Click to clear the "Enable Forms Based Authentication for Outlook Web Access" check box.
6. Click "OK".
7. Restart the following services:
- Microsoft Exchange System Attendant service
- IIS Admin Service

1. Clear the IIS server files follow these steps:
a. Go to the %windows%\IIS Temporary Compressed Files directory
b. Select all of the content in this directory and delete it.
2. Go to a command prompt, type "iisreset".

At the external client:
1. Please open IE and click Tools -> Internet Options
2. Select Delete Files and click OK to confirm that you want to delete the
content.

In addition, you may want to also try this:

Going into properties of the exchange directory in IIS (i.e. IIS/Web Sites/Default website/Exchange)
Click on the Directory Security tab, then click on Edit in the Authenication and access control.
Clear out the information in Default Domain and Realm boxes at the bottom. Leave the information in "Basic authentication." Leave the other boxes as is.

Another thought is there a global catalog in the same site as your Exchange back-end and what is the load on the GC?

Back to Software Forum
4 total posts (Page 1 of 1)  

Related Discussions

Related Forums