bduenges
asked on
Outlook Web Access takes too long to respond
We had an issue over the weekend with one of our certificates for OWA. In working with MSFT, we had to use a self signed certificate for our OWA site. Everything seems to be working with the site, however now when accessing the OWA site. The log in page comes up very quickly, but once I enter the username and password it takes anywhere from 60-70 seconds for the mailbox page to come up. That seems like a long time. Our OWA server sits on our CAS server and that connects to another server which servers has the mailbox server. Any help on what could be causing the issue is appreciated.
Suliman Abu Kharroub
Is the CAs server connected directly to the internet ? Public IP is assigned on the CAS or firewall with static nat or revirce proxy ?
ASKER
I should have prefaced. This is happening internally. Our OWA server does not public face. It actuallys sits behind our Sonicwall SSL Vpn server. Users on the outside log in to the SSL VPN and then go to the OWA server. So the OWA server is always being accessed internally. However, the issue is occurring when I am trying to access internally going through no ssl vpn appliance or FW.
What type of authentication do you use ?
please check if there is any update recently applied on exchange server (exchange updates not windows updates ).
please check if there is any update recently applied on exchange server (exchange updates not windows updates ).
ASKER
There has been no updates on the exchange server since last month. It has worked fine since them. Where would I find the type of authentication?
From exchange management console, Server config... client access.... OWA properties.
ASKER
Forms based authentication - User Name Only
Try the following:
1. restart Microsoft exchange form based authentication service.
2. reset OWA virtual directory.
1. restart Microsoft exchange form based authentication service.
2. reset OWA virtual directory.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Check to make sure in IIS for the Default Web Site that the interface chosen is not "Listen on all" and tie it directly to the correct NIC.