Microsoft Direct Access Teredo

Configuration has yet to be fully verified, Kemp Support will gladly assist if Epicor web traffic is not flowing as expected.

 

1   Introduction

IPHTTPS is typical 443 traffic that our deployment guide tells how to setup  (https://support.kemptechnologies.com/hc/en-us/articles/203343999-Windows-Server-R2-DirectAccess)

This is only compatible for Windows 8 and above clients. If a customer has Windows 7 clients, then they have to use another tunneling protocol such as Teredo. Teredo is a protocol that converts IPv6 addresses into IPv4 by using UDP packets and 2 consecutive external IPs.

By implementing a Kemp Load balancing solution, you will gain the ability to Load Balance your Teredo servers, which will enable High Availability by performing health checks, and will ensure persistent and efficient work flows to your cluster.

 

1.2  Document Purpose

This section details a configuration for a specific application that has been provided by  a customer but has yet to be fully tested.

This specific configuration will enable your Teredo environment  to be Load Balanced. 

Configuration has yet to be fully verified, but Kemp Support will gladly assist if Adobe Connect traffic is not flowing as expected.

 

2  Configuration Required

Two Separate virtual Services will be required, both using wildcard ports. Transparency is required to make this configuration function correctly. See Transparency guide here. https://support.kemptechnologies.com/hc/en-us/articles/203126369-Transparency

 

2.1 Global Configuration  

     >No Changes Required

 

2.2  Virtual Service Configuration:

 

2.3   Teredo1 Virtual Service 

      > New Virtual Service

      > Enter IP Address

      > Port = *

      > Name = Teredo1

      > Add New Virtual Service

 

2.4    Standard Options   

      > Enable Transparency

      >  Persistence = Source IP    

      >  Persistence Time = 6 Minutes

      > Scheduling Method = Round Robin

      >  Idle Connection Timeout = 660  (Default)

 

2.5   Real Servers

      > Checker Parameter Type = ICMP

      > Add New 

      > Enter IP Address of Tereno Servers

 

3.0   Teredo2 Virtual Service 

      > New Virtual Service

      > Enter IP Address

      > Port = *

      > Name = Teredo2

      > Add New Virtual Service



3.1    Standard Options   

      > Enable Transparency

      >  Persistence = Source IP    

      >  Persistence Time = 6 Minutes

      > Scheduling Method = Round Robin

      >  Idle Connection Timeout = 660  (Default)

 

3.2  Real Servers

      > Checker Parameter Type = ICMP

      > Add New 

      > Enter IP Address of Tereno Servers



If you have successfully Load Balanced your Tereno environment by implementing this specific configuration, please give a thumbs up or please leave a comment on a possible alteration that was required to make it function. Thank you

 

 

0

2 comments

Avatar

robin.vermeirsch

Is there a validated setup guide for Full Direct Access load balancing available? Are there templates available as well?

0

Avatar

MarkDeegan

Hello Robin,

Here is our setup guide for Direct Access on Server 2012. https://support.kemptechnologies.com/hc/en-us/articles/203343999-Windows-Server-2012-DirectAccess

Regards

Mark

0

Please to leave a comment.

Didn't find what you were looking for?