Hello everyone,
I'm setting up an Exchange 2010 environment as part of a migration from our single physical Exchange 2007 server. The 2010 environment looks like this:
2x Barracuda virtual load balancing appliances
2x Ex 2010 Standard CAS servers, in a CAS Array, virtualized
2x Ex 2010 Enterprise mailbox servers, in a DAG, virtualized
The virtualization platform is VMware 5.0. I followed Microsoft's documentation on setting up the 2010 environment and had no issues in any part of that setup. With the load balancers, I followed Barracuda's documentation on setting things up and even had them on the phone double checking and verifying the settings were correct, which they said they were.
The problem I'm experiencing is that when I move a mailbox into the 2010 environment and start up Outlook, I run into considerable connectivity issues. I'll explain further --
By default, it sets itself up in Cached Exchange Mode. From there, when Outlook opens, the pop-up bubble saying I've lost connection shows up within a minute or so. When I open the Exchange Connection Status screen (CTRL+Right Click on the Outlook icon in the systray) I can watch as the connections to my CAS Array address disconnect and reconnect. In the Req/Fail column, I see a number of Fail attempts alongside the Requests, and average response time is well within normal limits.
In the event log, the only thing I see on my client machine is Outlook information even 26; stating that Outlook has lost connection, then regained it. I'm seeing no errors on the Exchange even logs, and no events/warnings are showing up from the load balancers.
From Barracuda, they recommended that I disable one of the two CAS servers in the load balancer configuration. This would allow my client connection to choose a specific CAS server, as well as rule out persistent connection issues (so they told me). I had done this and to no avail. My next step was to open a ticket with Microsoft, but since it's late on a Friday, I think I'll wait until Monday and see what the community may come up with.
Many thanks,
Rick