DirectAccess Load Balancing Error

Hi 

Just seeing if anyone has come across the following error when trying to enable Network Load Balancing in DA 2012.

Error is The length of the prefix used to assign IPv6 addresses to DirectAccess clients connecting over IP-HTTPS should be 59 bits.

Any help would be good

Thanks

March 25th, 2015 11:25am

Hi,

By default, DirectAccess accept a /64 prefix for the IP-HTTPS range on a single server.
This is the IPv6 range for your clients.

When moving to NLB, you must use a /59 range because each DirectAccess server in the Cluster will receive a /64 range based on the range you defined in the console.

Let's say you implement a 2001::1000:/59, server1 will use 2001::1000:/64 for the clients, server2 will use 2001::1001:/64, etc...

Gerald

Edit: Carriage Returns problem on the forum when posting from my smartphone, will correct that later :-)

Free Windows Admin Tool Kit Click here and download it now
March 25th, 2015 3:11pm

Hi Gerald

Thanks for the reply.  I have set up a number of these load balanced DA environments but never had to change any IPv6 addresses.  is this something that is required in this instance?

Thanks

March 25th, 2015 5:41pm

Hi,

By default, DirectAccess accept a /64 prefix for the IP-HTTPS range on a single server.
This is the IPv6 range for your clients.

When moving to NLB, you must use a /59 range because each DirectAccess server in the Cluster will receive a /64 range based on the range you defined in the console.

Let's say you implement a 2001::1000:/59, server1 will use 2001::1000:/64 for the clients, server2 will use 2001::1001:/64, etc...

Gerald

Edit: Carriage Returns problem on the forum when posting from my smartphone, will correct that later :-)

Free Windows Admin Tool Kit Click here and download it now
March 25th, 2015 7:09pm

Hi,

By default, DirectAccess accept a /64 prefix for the IP-HTTPS range on a single server.
This is the IPv6 range for your clients.

When moving to NLB, you must use a /59 range because each DirectAccess server in the Cluster will receive a /64 range based on the range you defined in the console.

Let's say you implement a 2001::1000:/59, server1 will use 2001::1000:/64 for the clients, server2 will use 2001::1001:/64, etc...

Gerald

Edit: Carriage Returns problem on the forum when posting from my smartphone, will correct that later :-)

March 25th, 2015 7:09pm

Hello,

Yes it is.

Have a look there: https://technet.microsoft.com/en-us/library/jj134175.aspx

  • When NLB or an external load balancer is used, the IPHTTPS prefix cannot be changed to anything other than /59.

Gerald

Free Windows Admin Tool Kit Click here and download it now
March 26th, 2015 1:00am

Hello,

Yes it is.

Have a look there: https://technet.microsoft.com/en-us/library/jj134175.aspx

  • When NLB or an external load balancer is used, the IPHTTPS prefix cannot be changed to anything other than /59.

Gerald

  • Proposed as answer by Gerald Mathieu Thursday, March 26, 2015 5:39 AM
March 26th, 2015 4:58am

Hello,

Yes it is.

Have a look there: https://technet.microsoft.com/en-us/library/jj134175.aspx

  • When NLB or an external load balancer is used, the IPHTTPS prefix cannot be changed to anything other than /59.

Gerald

  • Proposed as answer by Gerald Mathieu Thursday, March 26, 2015 5:39 AM
Free Windows Admin Tool Kit Click here and download it now
March 26th, 2015 4:58am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics