Silo's Quick Host functionality allows customers to connect to the quickest host connection available, which may not always be one that is geographically closest to the end-user


Client Requirements

• Silo Windows client version 2.9.12 and newer
• Web Client


Silo Location Settings

Ensure that Silo for Safe Access is configured for more than one data center location

From the Silo Admin Console, navigate to [Manage] Policies > Advanced > Silo Location to review the location policy


Windows Registry (enabled by default)

Quick Host is enabled without any required changes to the native client registry. However, if you wish to disable the Quick Host functionality, you may do so with the registry updates detailed below:

 

Quick Host - Windows Registry (enabled by default)

        Windows Registry Editor Version 5.00


        [HKEY_CURRENT_USER\SOFTWARE\Authentic8,Inc.\Authentic8]

        "UseQuickHost"=dword:00000000 


UseQuickHost Settings          

UseQuickHost

Value

Quick Host Setting

0

Quick Host is set to OFF

1

Quick Host is set to ON

No Registry entry

When there is no UseQuickHost registry entry, then Quick Host is set to ON. This is the default setting for UseQuickHost



Silo Host Connection Process      

Quick Host ON/OFF

Silo Host Connection Process

ON

When Quick Host is ON, Silo begins the connection process to all set regional data centers, with the best available endpoint becoming the working connection

OFF

When Quick Host is OFF, Silo will attempt to use the closest data center, but may have the tendency of connecting to a random endpoint. This is determined by comparing the geo-location of the IP address (as determined by Maxmind), along with the coordinates of the application servers in our database table



Sample Log Entries

14:49:00.582 INFO: Establishing connections to Session Hosts and finding a quick one

14:49:00.582 INFO: Connect Monitor :waiting for a quick session host from 5 session hosts 

14:49:00.583 STATUS: Session Host 0 :Session will go directly to the server (app-gce-west-lb1.authentic8.com:443) 

14:49:00.583 STATUS: Session Host 1 :Session will go directly to the server (app-gce-east-lb1.authentic8.com:443) 

14:49:00.583 STATUS: Session Host 0 :Establishing Secure Session With app-gce-west-lb1.authentic8.com Port 443 

14:49:00.583 STATUS: Session Host 2 :Session will go directly to the server (app-gce-asia-lb1.authentic8.com:443) 

14:49:00.583 STATUS: Session Host 1 :Establishing Secure Session With app-gce-east-lb1.authentic8.com Port 443 

14:49:00.583 STATUS: Session Host 3 :Session will go directly to the server (app-gce-europe-lb1.authentic8.com:443) 

14:49:00.583 STATUS: Session Host 2 :Establishing Secure Session With app-gce-asia-lb1.authentic8.com Port 443 

14:49:00.583 STATUS: Session Host 4 :Session will go directly to the server (app-gce-asia-lb2.authentic8.com:443) 

14:49:00.584 STATUS: Session Host 3 :Establishing Secure Session With app-gce-europe-lb1.authentic8.com Port 443 

14:49:00.584 STATUS: Session Host 4 :Establishing Secure Session With app-gce-asia-lb2.authentic8.com Port 443 


14:49:01.238 INFO: Connection Info : Session Host 0 : Success, connection time 312 ms (app-gce-west-lb1.authentic8.com:443) 

14:49:01.238 INFO: Connection Info : Session Host 1 : Success, connection time 359 ms (app-gce-east-lb1.authentic8.com:443) 

14:49:01.238 INFO: Connection Info : Session Host 2 : Success, connection time 609 ms (app-gce-asia-lb1.authentic8.com:443) 

14:49:01.238 INFO: Connection Info : Session Host 3 : Success, connection time 593 ms (app-gce-europe-lb1.authentic8.com:443) 

14:49:01.238 INFO: Connection Info : Session Host 4 : Success, connection time 656 ms (app-gce-asia-lb2.authentic8.com:443) 

14:49:01.238 INFO: Connection Info : use Session Host 0 (app-gce-west-lb1.authentic8.com:443) for current session 

14:49:02.089 INFO: Client version is good.  Proceeding.



Additional Resources

Understanding IP Address Geolocation



Please contact Support for any additional questions