Forum Discussion
MVA
Jun 24, 2015Nimbostratus
We had this issue in Exchange 2010 with LTM 11.5.2 and it was attributed to our WAN optimizer - disabled optimization to the VIP and this resolved the issue for us.
We had this issue in Exchange 2010 with LTM 11.5.2 and it was attributed to our WAN optimizer - disabled optimization to the VIP and this resolved the issue for us.