I have to publish 3 exchange 2010 front-end servers (OWA,ActiveSync,RPC over HTTPS) that are configured with WNLB and are members of a CASArray.
If use WAF to publish the CasaArray, all connections appears to come from the internal IP of the SOPHOS UTM. NLB affinity use the client IP to balance requests between the NLB members, so all connections goes to only one of the 3 front-ends.
If I publish the 3 front-end using WAF load balance, that is a pure round-robin, I loose affinity
Without the option to act as a "transparent" reverse proxy , passing the client IP to the real web servers, WAF cannot be used to publish NLB web servers
This thread was automatically locked due to age.