Hi Andy, The second part you are not quite understanding is the client persistence. Port 389 would go from Client A to DC1, but port 636 could go from Client A to DC2 as the persistence is only locked to the individual port. Domain controllers will not like this and AD authentication will most likely fail.
The most important question is: Why load balance a DC? This is not recommended for many reasons. Two domain controllers in a properly configured Active Directory environment will automatically distribute their workload by design. Tim Rosenquist ---------- 5. Re: Setting up domain controller withloadbalancer (Le, Andy) Message: 5 Date: Thu, 26 Sep 2013 09:50:40 -0400 From: "Le, Andy" <[email protected]> Subject: Re: [Zenloadbalancer-support] Setting up domain controller withloadbalancer To: <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="iso-8859-1" Right now, I have two separate farms for each port depending on if its tcp or udp traffic. So right now, I have 7 farms for the different ports, I didn't add them together. I didn't quite understand your second part. Thanks. From: Emilio Campos [mailto:[email protected]] Sent: Thursday, September 26, 2013 9:49 AM To: [email protected] Subject: Re: [Zenloadbalancer-support] Setting up domain controller withloadbalancer For more than one port on the same farm you have to use l4 farms in other cases it would not work because you have to configure that the same client ip goes to the same backend when the same client run connections to different ports Regards El 26/09/2013 15:44, "Le, Andy" <[email protected]> escribi?: I'm testing something for a client and they recommend loadbalancer. So I have test DC and load balancer on a vm. Both with different ip. I have test the dc by itself and everything works fine. I setup a virtual nic for the interface. Setup the farms for the dc traffic with port 88, 53, 389, 636, and so on. I set the virtual port to those ports corresponding as well. Set the real ip server configuration to that domain controller's ip address. All the farms has green status, but when I go to test it, doesn't seem to work. I'm testing the DC through the virtual nic. I'm using ad explorer and if I go directly to the DC ip, works fine. If I do to the virtual nic ip, said server is not operational. Any mis-configurations I'm missing? -- Disclaimer: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damages caused by any virus transmitted by this email. ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ Zenloadbalancer-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/zenloadbalancer-support
