Forum Discussion
NimbostratusOutlook OWA TIMEOUT issue
Hello Guys,
Problem 1 :- I am facing Outlook Timeout issue ( duration at any time between 1 to 10mins) for Pubic Internet users with OWA Clients .
My Current setup : 1)Viprion F5 for Inside segment with iapp f5.microsoft_exchange_2010_cas.2012_06_08
Exchange server 2010 are mapped with servers 10.1.223.x1/x2/x3
Health monitors : Interval -60sec Timeout - 181 sec
Observation : when users connected from Inside LAN OWA never gets disconnected for 2-4 hrs ..etc even after after such 2-4 idle period.
2) BIGIP F5 for DMZ segment with iapp f5.microsoft_exchange_2010_cas.2012_06_08 are mapped to Inside segment same server 10.1.223.x1/x2/x3.
Health monitors : Interval -60sec Timeout - 181 sec
Observation : When users connected from Public host to access OWA they face intermittent disconnection during any time between 1-10mins and user login screen prompts.
Problem 2 :- MS Outlook 2003 Client cant connect to MSOutlook 2010 when we connect using F5 VIP address or hostname
however if we give direct Physical server ip address then Outlook 2003 Client connects sucessfully. I want to know does the above mentioned iapp rule can take care of the OLD Client connectivity.
Note : MS Outlook 2010 Client can connect to MSOutlook 2010 when we connect using F5 VIP address
Please go through the capture for more reference
Request you to please help me resolve the issue :( .
Regards, Akber Mirza.
8 Replies
Akber,
Our first recommendation is to use the new version of the iApp template available on downloads.f5.com. The template to use is named: f5.microsoft_exchange_2010_2013_cas.v1.2.0.tmpl. This version addresses many issues that were present in the version you are currently using.
With problem 1, which authentication method are you using for OWA? If you are using Windows/NTLM authentication, it is expected behavior that OWA does not time out and you must close the browser windows to log out. When using forms-based authentication, you should see a series of requests with "UA=0" in the URI. After the configured time has passed, you will see an HTTP 440 response from the server, at which time the client will be logged out.
There is an issue with cookie persistence that could be causing the public OWA disconnections; this is addressed by the latest version of the iApp.
On problem 2, there is no capture attached to this post. If upgrading to the latest version of the iApp template doesn't correct the problem, I recommend opening a case with F5 support.
thanks
Mike
Akber_Mirza_128Dear F5 Team & Experts,
can you Please respon to my Query .
Thanks , Akber Mirza.
- Make sure you use comments to respond to people (so they receive a notification).
- Akber_Mirza_128
Mike,
We are using the iapp " f5.microsoft_exchange_2010_cas.2012_06_08 " for Internal F5 and internal users never faces OWA Timeout issue .
The same Iapp is applied on DMZ for the Public host users during which the Public users facing OWA timeout issue .
Do u Still recommend me to go for new iapp ? or shall look for the actual root cause.
~ Akber Mirza.
Are you using the same version of BIG-IP on both the internal and external BIG-IPs?
Since there are so many updates and fixes, I generally recommend that customers upgrade to the new template in all cases. Since I can't see your capture information, it's difficult for me to find the root cause. If you open a support case, post the case number here and I will be able to look at the information.
- Akber_Mirza_128
Please refer the case no 1-277579837 and attached the all the F5, Client & httpwatch logs for yourreference which are updated with date 22nd aug'13 in F5 drop box.
- Akber_Mirza_128
Dear F5 team & Experts,
Please comment your valuable suggestion on this case.
Regards, Akber Mirza,
ghost-rider_124did your problem solved? I am facing the same issue
