Could it be due to sticky sessions? Like outlook still thinks that you are
connected to one server while on ZLB you had a session timeout and on the
next request to exchange you've been forwarded to another server. Another
server thinks what's up with that? A new client with not a login request?
Display credentials! Then probably some kind of sequence/IDs are be broken
in outlook-exchange protocol (hello MS) from a previous session - that is
probably why you stuck with OK button and client restart (to basically reset
connection). All load balancers will experience that if not configured
properly.
There is nothing really magical going on in the load balancing business.
Most of the problems are: not forwarding all ports/protocols OR session
timeouts and user is forwarded to another server that does not recognize the
user/session.
Basically, to solve your problem IMHO you must be sure that ALL your
requests (ports/protocols) go to the same server (I guess it's already done)
and your timeouts on ZLB are higher than on outlook/exchange. Can you find
out how on Kemp sticky sessions are configured for exchange?
Dima
From: Kerry Denten [mailto:[email protected]]
Sent: Sunday, January 5, 2014 10:45 AM
To: [email protected]
Subject: [Zenloadbalancer-support] Issues with Exchange 2013
Hi guys,
Loving the Zen Load Balancer. It's brilliant considering it's clearly still
a work in progress.
I'm very keen to use it in production, load balancing Exchange 2013, but I'm
having some issues.
If I use TCP on port 443 to load balance an array of 3 CAS which now only
require HTTPS to be load balanced, I keep experiencing issues where Outlook
keeps doing one of the following things:
1. A pop-up displays saying my password may have changed (which it
hasn't), but the client remains connected to the mailbox
2. The credential dialogue pops up, and no matter how many times OK is
clicked, reconnection does not occur without a restart of the client
Obviously, neither of these scenarios is ideal, especially when they seem to
happen in a cycle around every half an hour.
So, I tried configuring the Farm using HTTP on port 443, and no matter what
configuration I put in place, I either get a PEM certificate error from the
Outlook client, or I can't restart the Farm because of the configuration.
Commercial load balancers all work fine, such as Kemp etc, but they're cost
prohibitive, and while HAProxy works perfectly with Exchange 2013, without a
web UI, it's a pain to deal with, and I'm not paying Snapt-UI nearly $600USD
every year for the benefit of a web ui on an open source project.
Anyway, I'm a bit stumped. Is there any definitive help you can offer for
configuring Zen for use with Exchange 2013?
Thanks in advance.
Kerry
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Zenloadbalancer-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
