Problems with connection being passed through KEMP VS to Exchange host

0

Hello!
Please pardon the newbie nature of this question, but I'm stuck on a new test configuration of a Kemp Load Master. This is a single-arm installation as a proof of concept for a new Exchange infrastructure. I'm trying to pass a login and connection through to a test Exchange 2013 SP1 installation. I can connect directly to the CAS from a client but can't hit the virtual server interface. The statistics show no bytes received by either eth0 or eth1, and no traffic to the virtual interface.

I've followed the Exchange 2013 Deployment Guide as well as the WUI Guide, and both using and not using the Exchange template.
If there's another source of information or perhaps a known-good sample for a POC I'd be very grateful for the direction.
Thanks!
Gregg

5 comments

Avatar
0
Gregg Hughes

Update: I checked again and the real Server is enabled and all the VS's are showing.up.

Happy to supply further details as needed.
Thanks!

Gregg

Avatar
0
Christian Scheller

Hi,

you can take a tcpdump on the Loadmaster to help analyze the problem.

Go to System Configuration ==> System Log Files ==> Logging options ==> Debug Options ==> TCP dump

Start the trace and replay the connection attempt. Inspect the trace looking for RST packets as they would indicate where you're getting stuck at. Try enabling "Subnet Originating Requests" under Standard Options.

Avatar
0
Gregg Hughes

Hello, Christian!
I don't see the Debug options on the breadcrumb trail. Is this because I'm running the VMware virtual appliance? I checked on the console/SSH - there's no debut option there, either.

Thanks!

Gregg

Avatar
0
Gregg Hughes

Never mind - found it. Proceeding on with packet captures.

Avatar
0
Gregg Hughes

Hello, Christian!
After some poking around I was able to get the single-arm configuration to work by adding the virtual IP to the interface definitions and I was able to get to OWA. Now, on to configuring RSA Securid!

Thanks!

gregg