Hello everyone,
We are experiencing strange problem with ARR + Exchange 2013 DAG. Exchange DAG is configured only internally, no publishing to internet, there are two servers in physically separated locations connected over site-to-site VPN. We would like to use ARR as a workaround for web services availability until we figure out do we need "real" Exchange load balancer.
ARR is configured by practices from Technet articles. When we alter hosts file at workstation and point Outlook to ARR we manage to connect sometimes but connection is interrupting almost every second. Fiddler is showing that EWS virtual directory is returning 502 (Bad Gateway) errors which, from what i can see on internet, is probably 401 error which ARR maps to 502. When users are pointed directly to Exchange servers everything works great.
Exchange is configured by best practices*, certificates are exchanged, ports also, ARR rules are ok, timeouts and recycling is configured, health monitors are passing tests, everything seems to be in place but Outlook is not having stable connection.
*Except one thing. Wildcard certificate (plus "owa" and "mail" subject alternative names) is used and guy who configured Exchange at first configured all services to respond on name that is not explicitly named in certificate, can this create problem with ARR? Once again, it works perfectly well without ARR.
Also, do i need other certificates on ARR server beside SSL? Maybe "default" Exchange certificates?
I also found update for ARR but it seems that it only applies on Server 2012 while we are working on 2012R2
I know it's long shot but could anyone point me in right direction?
Thanks