jdewing
Feb 24, 2011Cirrus
RPC Client Access
I'm having an issue getting outlook client to work with RPC Client Access. I follow the steps from the F5 Deployment Guide "Microsoft Exchange 2010". Everything is working with OWA and Hub Transport,...
On Friday I tested OWA.
I went to cas1, cas2 and cas3 and all worked fine. I went into the LTM and disabled pool members cas2 and cas3 for the OWA POOL. tested owa.mydomain.com and I received javascript errors hitting cas1 through the LTM. I repeated the process, disabling cas1 and cas3 in the LTM and went to owa.mydomain.com and it worked fine hitting cas 2 through LTM...again, cas3 through LTM was fine...I figured the problem was specific to cas1 and decided to leave it disabled until I could look at it this morning (I have a bunch of other issues I need to work through so it wasn't high priority).
This morning my colleague in Wisconsin tested hitting either CAS2 or CAS3 through the LTM (not sure which because both were enabled) and he received JS errors. I tested and I did NOT receive JS errors. I gave him my test account credentials to ensure it wasn't an issue specific to an account and he still received JS errors. Whatever the issue is, it seems to be specific to the LTM and it's VERY sporadic.
I remember encountering this problem when we were deploying the LTM to begin with. I would report to my colleague that OWA was hanging and he would test it and it would be fine...I would go back in and it was no longer hanging.
I have some other issues to work through first but if I cannot find a quick answer for this I will put in a ticket with F5 and report back to you.
respectfully,
Ken