http://blogs.technet.com/b/edgeaccessblog/archive/2010/05/17/configuring-an-external-load-balanced-uag-directaccess-array-for-an-ipv4-only-network.aspxThe article Configuring external load balancing for a Forefront UAG DirectAccess array at http://technet.microsoft.com/en-us/library/ee690463.aspx describes how you would configure a UAG DirectAccess array when using external load balancers. In the exampleen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.technet.com/b/edgeaccessblog/archive/2010/05/17/configuring-an-external-load-balanced-uag-directaccess-array-for-an-ipv4-only-network.aspx#3509406Tue, 17 Jul 2012 18:01:03 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3509406Fred<p>This looks great, but how about &#39;Manage Out&#39;? Without the HLB on the inside, how do you get the internal clients to load balance across the UAG servers? Do you simply point them all at the one server and forget about load balancing on the internal side? Then of course there is ISATAP - since the UAG will not configure itself as an ISATAP router with HLB where does that go/point to facilitate &#39;Manage Out&#39;. I feel that this document is great for inbound access but does nothing in describing the full DA solution... </p> <div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3509406" width="1" height="1">http://blogs.technet.com/b/edgeaccessblog/archive/2010/05/17/configuring-an-external-load-balanced-uag-directaccess-array-for-an-ipv4-only-network.aspx#3362664Mon, 18 Oct 2010 17:12:32 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3362664Lux<p>Thanks for this, but I noticed a typo, </p> <p>&quot;192.0.2.31</p> <p>W = 192</p> <p>X= 0</p> <p>Y= 2</p> <p>Z= 30&quot;</p> <p>Should Z=30? or 31? and does it matter which IP on the external LB is used (1st IP or the 2nd Sequential IP)</p> <div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3362664" width="1" height="1">