DirectAccess Single NIC Load Balancing with Kemp LoadMaster | Richard M. Hicks Consulting, Inc.
In this scenario, the LB's int0 is Internet facing and int1 is on the DMZ along with the single nic DA servers, correct?
IOW's, the LB isn't configured with int0 on the DMZ and int1 along with the single nic DA servers on the production network.
We're seeing strange behaviour with Single NIC DA servers sat in a DMZ as a load balanced pair of servers behind the VIP of a Kemp Load balancer. When we establish a successful connection to one of the DA servers, if we gracefully shut down the DA server, the client machine acknowledges the loss of the DA server but sits continuously at "Connecting". The only way for the client to successfully reconnect to the remaining active DA server is to reboot the client. Once the client has been rebooted, it establishes a new connection to the remaining available load balanced DA server. Have you ever seen this behaviour before?
In this state when the UI reports "connecting" have you confirmed that connectivity is actually broken? Or are you relying solely on what the UI is reporting?
First of all, thanks for all the work you put into this log. It has helped me on several occasions with DirectAccess deployments.
Just to make sure, this should also cover the scenario where I have two single NIC DirectAccess servers in the internal network zone and the Kemp LoadMaster is in the DMZ with a single NIC, only? What about IPs? Say my internal DA servers have IPs 192.168.1.11 and 192.168.1.12. Before I set up the cluster, I gave DA1 the IP 192.168.1.10, which then became the cluster IP. The single NIC LoadMaster in the DMZ has 172.16.0.100 as the VIP for traffic to the DirectAccess servers, and the IPs 192.168.1.11 and 192.168.1.12 are configured as "real servers".