First off, this is a Free LoadMaster running on Hyper-V, which is an excellent platform, and I've got no complaints about this itself.
But, just wondering if anyone has any ideas. We started publishing our new Exchange 2013 environment as a load-balanced object on our firewall appliance. The appliance got upgraded, which broke load-balancing on it. The vendor is aware of this and is due to issue a fix soon, but in the meantime I've got the Kemp working as a load balancer so our firewall only needs to see it as a single device, rather than trying to load balance our Exchange servers.
This worked fine in testing for webmail- we have another public-facing DNS name which we used to try with webmail and it was fine, the Kemp was passing OWA no problem. When we put this live, OWA and SMTP worked great from outside, but we were unable to connect to Outlook internally. This would fail either by trying to point DNS at the public-facing address, or by going straight to the Kemp. All the time, the Kemp was handling external 443 and SMTP without issue.
Can anyone think of any issues that may have been stopping the Kemp accepting internal hits from an Outlook client? I've got SSL acceleration turned on with re-encryption so that the correct certificate is published.
Just too re-iterate; my actual problem is with our firewall appliance and not the Kemp, which has been so easy to configure and is doing it's job, I've obviously just mis-configured it. The LoadMaster was "thrown-in" and I have no training, so I'm just digging around in case there are any really obvious fixes to try.