New iApp, Exchange 2010 and SSL bridging

We're having an issue sending private messages right now, but we will be in touch soon via DevCentral.

 

 

In the meantime, can you please open a support case with F5 for this so we can track it internally?

 

 

What browser(s) are you using? I can suggest a few tools that can let us look inside the traffic, but need to know what platform we have to work with.

 

 

Are you able to create a new virtual server on another IP address? We'd like to try an experiment. If you can, please do this manually, rather than using an iApp template. Create the virtual with these characteristics:

 

 

Type: Performance (Layer 4)

 

Destination: Host, with whatever new IP address you have

 

Service Port: https

 

SNAT Pool: Automap

 

Default Pool: the pool that was created by the iApp template, likely named [somename]_owa_pool

 

Default Persistence Profile: source_addr

 

 

Then use a local Hosts file entry to make your client use the new address for the FQDN you have assigned to OWA.

 

 

This setup makes BIG-IP LTM do almost nothing to the traffic other than translate the destination IP (that's inherent to any Host-based virtual server) and translate the source IP to avoid asymmetric routing situations. If you can't get to OWA this way either, it points heavily towards a network topology issue, server configuration issue, or something of that nature. If you *can* get to OWA this way, then we can look more carefully at LTM configuration or some possible Exchange changes. Either way, it will give us more information to work with.